Pradeep
Storage? I am Storage!
Fortunately without the inherent doubling of failure rate
James said:I'm afraid I sort of see dual CPUs as being the IDE RAID0 of extra day to day performance, if you get my drift.e_dawg said:But if you and others are suggesting that there is no extra responsiveness during multitasking, then my whole point of wanting a dual CPU setup is gone.
flagreen said:"Real men sleep on rocks."
Mercutio said:flagreen said:"Real men sleep on rocks."
No no no.
Real men sleep on jagged rocks.
Or broken glass.
Or beneath real women.
James said:Oh, it's stable and all that - not like IDE RAID0 - but I was alluding more to all those SR newbies putting in RAID and expecting their day to day performance to go through the roof, and it doesn't. It's the same with dual CPUs IMO. If you have a specific use that is helped by 'em, by all means go for it. If you're just an average user looking for the Tim Allen "more power" experience, you're looking in the wrong place.
Your problem, o doggy one, is not the lack of a second CPU. It is the lack of a decent multi-tasking OS. All jokes aside, no version of Windows that I have ever seen can multi-task particularly well.
Tea said:what is the point of 512MB DDR, X15 and Athlon XP 1800 for a machine that spends its entire life running an email client and a handful of web browsers?
PS: if you still think I'm an OS snob, well, you just ain't ever met a Linux user. And as for Mac users ... well ... We will say no more.
I say that Acrobat distilling is not dual processor aware (I just gave it a try) and is CPU bound. Ditto Javascript. You'd be better off buying either a faster CPU or two faster computers and networking them than a dual CPU machine.e_dawg said:No traditional dual CPU applications in mind (like rendering, for example), but I very much dislike how my computer is unresponsive when the CPU is pegged at 100% by various processes while multitasking.
[...]
This, to me, is multitasking by water torture. If a dual CPU setup will allow me more responsive multitasking and minimize those "frozen CPU" moments, that is all I am asking for.
What say you, James?
Tannin has been well schooled. He seems to be confused about a number of related issues, which makes it difficult for him to articulate a strong position on this matter.time said:That statement will probably earn Cas' ire.
James said:I say that Acrobat distilling is not dual processor aware (I just gave it a try) and is CPU bound. Ditto Javascript. You'd be better off buying either a faster CPU or two faster computers and networking them than a dual CPU machine.e_dawg said:No traditional dual CPU applications in mind (like rendering, for example), but I very much dislike how my computer is unresponsive when the CPU is pegged at 100% by various processes while multitasking.
[...]
This, to me, is multitasking by water torture. If a dual CPU setup will allow me more responsive multitasking and minimize those "frozen CPU" moments, that is all I am asking for.
What say you, James?
Or four instances if you have dual Prestonia Xeons.The JoJo said:Yes, you can have multithreaded programs (written some) , but you can also run 2 instances of a singlethread program when you have 2 cpus.
The problem is I think that you guys don't realise that XP doesn't (reliably)farm out CPUs to applications based on which is the least busy. (At least, I can't get it to do that unless I set processor affinity individually for applications beforehand based on the order I'm going to launch them.) It's not like there's a pool of twice the available CPU power which is doled out as required.e_dawg said:I am with i and The Jojo on this one (maybe the blind leading the blind, but the rationale seems logical). If Acrobat maxes out a single CPU, can I not use the other CPU to zip around in Windows and work on other apps? That is the whole point -- not making Acrobat run faster, but making everything else run "not as slow" when Acrobat is tying up CPU #1.
I'm not Cas, but that's my reading of it. BeOS was designed from the ground up as a multi-CPU OS, NT was not - or, at least, it has to be backwards compatible with a lot of applications that are not.time said:I'd be interested to hear what Cas has to say about this. He has previously disparaged BEOS as offering no advantage over NT, yet I am under the impression that it was rather good at load balancing, and supposedly the API encouraged all apps to be multithreaded.
Cas, is the problem solely down to the way NT apps are written?
I was keeping quiet, but since you mention it... The general rule is that on an AS/400 a.k.a. iSeries, SMP overhead is as little as 4% of each additional CPU. For instance, a dual-processor model 730-2066 has a performance rating of 1050. The 4-way version, 730-2067, has a rating of 2000, netting a loss of 4.76% due to SMP overhead. There are a handful of hardware white papers at http://www-1.ibm.com/servers/eserver/iseries/whpapr/#hardware although most are a couple of years old and could use some updating.Mercutio said:Without exception I can't think of an operating system that handles multiple CPUs really well and really gracefully. They're all basically retarded when it comes to that.
OK, since fushigi will probably come by and mention it, mainframes OSes do it pretty well (mainframes are lots of little CPUs).
Even in the case of applications with careful SMP support, this metric is very application specific. Certainly, very low common resource contention would be required to maintain an SMP penalty below 5% for an arbitrary number of CPUs. Any lower, and it would seem that multiple individual machines would be a better solution.Fushigi said:The general rule is that on an AS/400 a.k.a. iSeries, SMP overhead is as little as 4% of each additional CPU. For instance, a dual-processor model 730-2066 has a performance rating of 1050.
Certainly, you wouldn't want a system that limited threads in some arbitrary way, but I hope most readers realize what an absurd number even 40,000 threads is.Fushigi said:IBM has benchmarked the prior generation of hardware at over 400,000 concurrent threads;
I used to design real time operating systems for a living. More recently, I have worked on general purpose operating systems as well.The JoJo said:...what do you do for a living cas?
Of course it's absurd. As far as I can tell, they did it to prove what the system can handle without barfing all over itself. The AS/400 has a history of being a closed, proprietary system. While that was true enough back in the early 90s, the iSeries today is the most open platform on the market bar none. Within a single chassis it can run multiple OS/400 invocations (including multiple OS versions), most AIX apps (true AIX coming by 2004), 64-bit PPC Linux, and multiple Windows NT/2000 servers all at the same time. The zSeries can't even do this.cas said:Certainly, you wouldn't want a system that limited threads in some arbitrary way, but I hope most readers realize what an absurd number even 40,000 threads is.
The ideal number of threads for a process in a 4-way machine is exactly 4.
Fushigi said:A good deal of that is because IBM doesn't know how to properly market the machine.