Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I don't know that it actually performs more simulations/calculation in the same time, but it can finish a given WU much faster than a typical single-CPU setup. It lets Stanford get wome work units done much sooner. In any case, it's valuable enough to Stanford to get those results fast that they've put quite a hefty points bonus on those WUs.Why is it faster, even under VMWare, than multiple instances of the regular client?
VMware has fairly low impact on CPU-intensive things like FAH, and since the SMP client works on one job with four cores (or two, due to limitations on VMware's free product) it gets that single job done faster on average than two cores working on two jobs.Why is it faster, even under VMWare, than multiple instances of the regular client?
Yep. It may be made accessible over SMB shares - \\vm\fold - but I don't think monitoring files for changes works as well as would be hoped over network.Anyway, I suspect that the problem is it will run on the virtual machine, writing its log to a file on the VM's simulated hard drive -- and not anywhere YURT can actually see it. Perhaps, if a Windows version is made available, I can look into making YURT compatible with it.
Thank you for your kind words. I'm hoping that I can get the per-user graphs up today or tomorrow, and then work on getting the whole thing automated.unhappy_mage said:I like the new graphs! It makes it quick and easy to see what kind of output you're getting from an individual box.
Er, but two processes working on two jobs has the same overall completion rate as the SMP client, right? Or is there some performance win in the algorithm the client uses when it can throw two processors at the same work unit?unhappy_mage said:and since the SMP client works on one job with four cores (or two, due to limitations on VMware's free product) it gets that single job done faster on average than two cores working on two jobs.
Er, but two processes working on two jobs has the same overall completion rate as the SMP client, right? Or is there some performance win in the algorithm the client uses when it can throw two processors at the same work unit?