Davej said:
I found this cpu lookup, which is adequate...
http://www.cpubenchmark.net/cpu_list.php
Yes, those are multi-threaded benchmarks.
Not all application software, is capable of using
all the cores in a processor in parallel. In such
cases, the above PassMarks don't tell you everything.
We used to rely on SuperPI timing benchmarks, as
a measure of single threaded performance. The
hwbot.org site has a large number of these results,
but the interface to the information makes it
very difficult to get what you need. The problem
with that site, is 99% of the SuperPI results
are for overclocked processors. Hardly
any benchmarks exist for "stock" operation.
Still, it's the only other site I know of,
that can help predict single-threaded
performance. Most of the software on
my computer is single threaded. Photoshop
would be one of the exceptions (where half
the filters are single-threaded for numerical
accuracy, and the other half are multi-threaded
for speed).
Movie editing and rendering, is another area that
uses multiple cores to good effect. If you're buying
a computer for movie editing or transcoding,
then the PassMark results above are the
benchmarks to use. But for other purposes,
SuperPI is my choice (since much of my software
is older, and no effort was made to get it to
execute in parallel).
Recent versions of Excel, do some calculations
in parallel, but then other sections are still
single threaded. Engaging parallelism, isn't
always the easiest thing to do. And some applications
with parallel execution, don't scale to an infinite
number of cores. Perhaps the 7ZIP compression option
you've selected, runs at most two threads, and only
uses half of the processing power of a four-core
processor. From that perspective, PassMark over-estimates
what you're buying. There could be wasted capacity
you cannot use.
It's just like Cinebench, which is a "perfect scaling
application". Cinebench as a benchmark can use a large
number of cores, which may not be representative of
how the rest of your software works. The reason Cinebench
can do that, is the threads of execution don't talk
to one another. Real-world applications have more
need to synchronize the threads of execution, which slows
them down (waiting for the slow thread to finish).
Paul