The Advanced Assembly Optomizations should be on by default. If you find that they aren't, the client has turned them off as a result of having a problem in crunching the current WU. The AAO should turn back on with the start of the next WU, again provided there aren't any problems.
Typically, one should NOT have to run the forceasm flag. The risk is that if the problem persists, you may end up with corrupt work and therefore it being rejected. So proceed with caution, monitoring the work. If you find that you must run the forceasm flag in order to complete a WU, one should report such in the folding-community.
Last edited by BuiesCreek847; 05-05-2003 at 01:25 AM.
That's not what "-forceasm" does. Recently, Gromacs units have been publicly (not beta or advanced beta) released. They feature assembly optimizations that will increase speed by up to 300x on SSE and 3DNow! enabled CPUs. "-forceasm" will force these optimizations on. It is only needed if they have been turned off, which the client will do after a Gromacs core crashes 4 times in a row (number may have been changed). So "-forceasm" is really only needed if you've had crashes and Gromacs has disabled assembly code. It will in the newest versions re-enable extensions after a WU completes sucessfully without them, I believe.
Myself, I run "-forceasm" and "-verbosity 9". Most people should only use "-forceasm" because "-verbosity 9" really isn't needed. Except, of course, if you're like me.
Well, for what it's worth, I do believe that assembly optimizations are disabled the first time the client crashes or terminates abnormally. I do recall having heard of the 4 time thing, but from my experience, it is the first time everytime.
I just uploaded an updated version of the service setup that includes the option.
You just need to dl it from here and unzip it, double click the reg file and then click yes. Restart the service and you're good to go.
Originally posted by Tigsman If you installed the service manually, just add -forceasm to the end of the 'AppParameters' key value field. i.e. it should be '-service -forceasm"
Tigs, after doing that, when you start the service again it corrupts that wu that you were working on. I don't know if it's just mine or not, but I'd suggest until you've completed and sent a WU before you edit it manually.
Originally posted by lbwarped Tigs, after doing that, when you start the service again it corrupts that wu that you were working on. I don't know if it's just mine or not, but I'd suggest until you've completed and sent a WU before you edit it manually.
I haven't had problems switching it on in the middle of WU.