On Tue, 25 Jan 2005 22:32:47 GMT, "Richard Williams"
<(E-Mail Removed)> wrote:
>newbie here.
>
>i'm trying to decide as well when and what to buy.
>
>very helpful info. Can you give an example(s) of software that is
>multithreaded?
Uhh.. that's a kind of broad question. Damn near any software CAN be
multithreaded if it's written as such. In fact, I should probably
specify my original statement a bit more in that I'm only referring to
software that makes use of multithreaded code in an effective manner
to increase performance. Pretty much all software has multiple
threads, but mostly all of the threads but one sit idle 99.9% of the
time. FWIW if you check in Task Manager under the process tab you can
add a column to see how many threads are being used.
As for some common examples of multithreaded software, well first off
pretty much ALL server software. You're standard server application
opens each new connection to it as a separate thread. Other common
examples of heavily multithreaded software are high performance
computing applications, which often get split up into groups of
calculations to be distributed among many processors.
More down-to-earth software that is multithreaded included many
(most?) Photoshop filters, some audio and video encoders, most ray
tracing programs, and many, many workstation applications of various
types. Basically any task that can be effectively split up into
multiple chunks can be multithreaded, though whether it was programmed
as such or not is up to the developers.
The following is a article that compares some dual-processor systems.
If you read through the benchmarks at the end you'll see that there
are some applications in which the dual-processors systems do VERY
well; those applications are multithreaded. In other tests the single
processor systems are as fast or faster because the applications are
not multithreaded:
http://www.tomshardware.com/cpu/20030422/
-------------
Tony Hill
hilla <underscore> 20 <at> yahoo <dot> ca