- Joined
- Feb 2, 2001
- Location
- Roanoke, VA
Does the FAH client support SMP? I am actually running it on a couple of dual CPU workstations, but it doesn't seam to be using SMP. Is there a way to enable it? Thanks.
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
soundfx4 said:ok, but what about CPU utilization? If I set it to 100% and only ran one instance, wouldn't windows distribute the load to about 50% on each CPU. That is how SMP works to my knowledge, unless of course a program supports SMP, in which case it can utilize both CPU's simultaneously at 100%. Is that correct?
If so, then if I set one instance to 20% utilization, then only 10% of each CPU would be used. So If I ran two instances with 20% utilization, then that would make
Instance number 1: CPU 1: 10% CPU 2: 10%
Instance number 2: CPU 1: 10% CPU 2: 10%
Is that right? I can't actually run it at 100% on the two dual core workstations, because they are actually servers, and they need extra CPU time to do other stuff.
Thanks!
Adak said:No. Windows will NOT distribute a folding program load across two cpu's or cores. It will run whatever percentage you have it allowed to run at, on just one core/cpu per instance.
Yes, that is theoretically how SMP programs work (not in real life, certainly), but the folding program is not SMP.
Again, if you set one folding instance to 20% it will run 20% off just ONE cpu or core, and NOTHING off the other.
Yes, you CAN let the folding programs run at 100% BECAUSE THEY HAVE IDLE PRIORITY, and will almost instantly give up CPU cycles. This has been well tested and documented.
The only problem would be if you had a very memory intensive work unit (like the old QMD's), then the problem becomes the memory the folding program will use AND KEEP, NO MATTER WHAT. It WILL give up the CPU cycles, immediately, BUT IT KEEPS IT'S MEMORY. So memory usage is what you have to watch.
Adak
TollhouseFrank said:only 1 of the cores is quasi-smp compatible, but even then, it only gives about a 5% boost in power... and that is the QMD Core.
soundfx4 said:now that you say that, I know for a fact that what you are saying is not true. I wasn't sure at first, but I remember now having a long heated debate on what you are saying, and finally I understood how it works. Windows does and WILL distribute load across all CPU's evenly. That's just how it works. Ask...ummm...well I forgot his name lol, but he is the one that told me NO, NO! That is wrong! And I was all like, but that doesn't make any since! And finally after we were on the same page, I understood what he was saying, and I realized that windows does indeed evenly distribute the load across all cores/cpus.
LandShark said:yes. running single instance on a dual core/HT'ed machine will only shows 50% usage in task manager 'cos windows see it as 2 core thus 50%+50%=100%. however, it doesn't mean one core is working 100% while the other core is sitting idle when running 1 instance on a dual core rig tho!!
p.s. it will be true (1 core sitting idle while the other one is running hard) in the case of Win98's old day as it can't see more than 1 cpu.
however, it doesn't mean one core is working 100% while the other core is sitting idle when running 1 instance on a dual core rig tho!!
yes, windows won't/can't make a non-SMP aware programe into a multi-thread program. however, windows WILL split the load (in whatever % it seems approperiate) on even just one single thread through out 2 core. it will not letting one core doing all the work (1 thread) while the other is sitting idle. e.g. it will be like 20% on core1, 30% load on core2 for the single thread instruction.Adak said:Even though there are two cores, a non-SMP program will only use one of those cores. The program simply isn't SMP, so it can't use more than one core. That is determined by the application program, NOT by the OS.
If that program should launch another program thread, THAT new program may very well be used by the second core.
Windows WILL assign different programs (and different instances of the same program), to each core, as it judges best, but it will NOT make a non-SMP program into an SMP performer.
Adak
LandShark said:yes, windows won't/can't make a non-SMP aware programe into a multi-thread program. however, windows WILL split the load (in whatever % it seems approperiate) on even just one single thread through out 2 core. it will not letting one core doing all the work (1 thread) while the other is sitting idle. e.g. it will be like 20% on core1, 30% load on core2 for the single thread instruction.