Last edited:
SiriusB said:Does this mean the Linux SMP Guide isn't needed any more?![]()
According to http://forum.folding-community.org/ftopic18534.html
kasson says
Quote:
Currently we have dedicated win SMP work units. Three projects are being assigned at this time:
Project 2610: 1523 points, deadline 4 days
Project 2651: 1760 points, deadline 4 days
Project 2652: 1148 points, deadline 3 days
Particularly as this is a beta client, we reserve the possibility to adjust point values and/or deadlines in the future.
Might as well install this. Just started another 1760 pointer though, will have to wait another 32 hours for it to finish.Steevo38 said:Now getting 13.5 mins per frame on my E6300 @3.15
So roughly 1870ppd here.![]()
Fantastic to see that's still an issuediogenese said:How do you close the thing down without it having a paddy when you restart it and get "improper shutdown" messages?
From the known bugs list - linky19) Unless you plan to reboot, when you stop the client with CTRL-C be sure that the processes FahCore_a1.exe and mpiexec and/or smpd have stopped. Many folks are finding that they need to kill mpiexec manually and or stop/start the smpd service. If you restart the client without doing this, the WU may be deleted. A common message is MISSING_WORK_FILES.
on a quad core it's alright - on a dual core it's not a good idea at all2bullish said:I take it this client runs at 100% cpu usage, therefore, running this and the gpu client is redundant?
edit: and just noticed this tooThe SMP core can get confused about disabling SSE, so we suggest running with the -forceasm flag if you notice that the SSE was disabled unnecessarily.
6) The SMP core can get confused about disabling SSE, so we suggest running with the -forceasm flag if you notice that the SSE was disabled unnecessarily. In fact, SSE will re-enable itself even though the messages say that isn't happening, so -forceasm is no longer required.
In the updated Known Bugs list they now say it's not necessary to use -forceasm, it can't hurt thoughdiogenese said:I've just found on the Stanford site that they recommend the use of the -forceasm flag.
6) The SMP core can get confused about disabling SSE, so we suggest running with the -forceasm flag if you notice that the SSE was disabled unnecessarily. In fact, SSE will re-enable itself even though the messages say that isn't happening, so -forceasm is no longer required.