The problem is not whether a program can be parallelized, but whether it needs to be parallelized. Human being can not tell the difference of 10ms and 20ms, if it's fast enough, you don't need more performance. Today's PC's at that stage for most programs. Name commonly seen desktop program which can benefit from multi-threading and haven't.
parallalized.
【在 a****l 的大作中提到】 : you will rarely see a program that is strictly sequential thus hard to use : multi-threading. There are always works in a program that can parallalized. :
a*l
9 楼
the programs that need performance boost most are not desktop applications. Actually, I am using loptop applications (windows, browser, text-editing) on a very old computer, and it's not too bad at all.
【在 g*****g 的大作中提到】 : The problem is not whether a program can be parallelized, : but whether it needs to be parallelized. Human being can : not tell the difference of 10ms and 20ms, if it's fast : enough, you don't need more performance. Today's PC's at : that stage for most programs. : Name commonly seen desktop program which can : benefit from multi-threading and haven't. : : parallalized.
g*g
10 楼
Then what are you arguing about? I guess you don't read my post at all.
.
【在 a****l 的大作中提到】 : the programs that need performance boost most are not desktop applications. : Actually, I am using loptop applications (windows, browser, text-editing) : on a very old computer, and it's not too bad at all.
Yeah, I'd be careful with this "never" business, too. 8-) Lots of non-trivial desktop applications today already run multiple threads. It's just we don'g feel it because most of those threads are an once-off thing that does a particular job - for instance, Word uses a worker thread to do pagination. Acrobat Reader uses a background thread to keep loading the rest of a large pdf file while the user views the first pages.