NEW WIN SMP CLIENT
SPIKE09
Scatland
the current win smp beta has expired next time you stop it it won't start. news here and here
http://foldingforum.org/viewtopic.php?f=24&t=4372
http://foldingforum.org/viewtopic.php?f=24&t=4270
http://foldingforum.org/viewtopic.php?f=24&t=4372
http://foldingforum.org/viewtopic.php?f=24&t=4270
0
Comments
When/Where were you supposed to add that. I added -smp when it asked for advanced commands, but apparently that was not the time.
// ok I got it now. I followed this guys directions and got it to work.
What is the consensus on the disable cpu affinity lock setting? Yes or no?
I've read that the answer may be different whether you're running intel or amd.
I am running a Q6600 BTW
Also, these three specific (new) config variables:
Disable CPU affinity lock [no/yes]? (doesn't seem to have an effect on this cpu)
Additional client paramaters []? (this is where I set the "-smp" flag)
IP address to bind cores to <for viewer>? (no clue)
edit\ same questions being asked here http://foldingforum.org/viewtopic.php?f=46&t=4471
The following I've found to be the best, that is high performance with good stability for single and double client Q6600 systems:
-- leave the Affinity entry in the config file at default, which is "No"
set the -SMP" flag in "additional parameters," or it will fold on only one core; of course, set the -smp flag in the shortcut properties of you start file shortcut if you use one
For systems (Q6600) running two WinSMP clients, same as the above, but install and run Affinity Changer. Based on my systems' performance, I believe Affinity Changer is just as important with the 6.22 client as it was with the 5.92. AF should bring you anywhere from 20-30% more production.
Cheers Leo, I have it and it only uses one core. Where exactly do I put the flag? I've had a lot of messing about so far and I'd like to avoid any more.
I've done that but now get this whenever I try to start it.
Cheers.
Indeed. And, if I'm reading this right, I'm wondering if they are trying to merge all their clients into one- unicore, multi-core, GPU, etc.- the version numbers seem to be converging as well (6.2 GPU, 6.22 SMP).
There are Yins and Yangs to that, but getting the operation to behave with the configuration is why a lot of software programmers have full-time jobs.
This update was ... not fun.
Hey, guys, we've just got to remember that WinSMP and GPU2 are beta projects. Stanford, Vijay & Co. realize it's a pain. That's one of the reasons the points rewards are so high for both of these clients. That's also why these clients can only be downloaded on the advanced users page, "For expert Folding@home donors."
Any of you guys run into that yet?
Hopefully it sorts itself out, or I'm just churning through core downloads all day.
While I understand this is a beta project, I don't understand why there are so many problems with this release, in all the time I've been folding, I don't recall another release that had this many issues. I wonder if they just tried to incorporate too many updates/fixes into one update.
Damn thing froze hours ago and I only just noticed. Then it can't pull down and unzip an old core, so it just sits there with its thumb up its ass and makes a mockery of my idling hardware.
Edit: just deleted everything and ran it as administrator (would have been nice to have that anywhere in the notes) and trying it out; we'll see if it works this way. Leaving it overnight, I'll curse more in the morning if it fails me.