forceasm and advmethods with 4.00
kanezfan
sunny south florida Icrontian
what do those two flags do, and do I need to run them on athlon xp based machines running the 4.00 console (not graphical) client?
0
Comments
What it does is forces F@H to use SSE instructions to help increase the performance of the processor.
-advmethods requests gromac units, which are generally worth more ponts and can be crunched more quickly.
I run them on my AXP machines, but some people have reported issues with -forceasm (and I guess -forcesse might have similar issues) with AXP systems.
The -advmethods gets you semi-beta WUs which have gone thru internal stanford testing, a beta team test, and is now out for the general public to get. They may not be quite as stable as the ones you can get with no flags tho.
One side note, if you get big gromacs, look at your core_78 version in log after you start gettign assinged larger gromacs WUs. If, after that, you still have Core_78, you can pause the client and will likely end up with Core_78 of release version 1.55. That version kicks butt with big WUs, it does them in about 90 to 80% of the time the 1.54 core with SAME switches did. Little ones, it is not so much better with, not so much improvement.
If you get something with an oddball never-seen-this-kind before that might have a number in the mid-to-high 800's or low 900's above 920, your box wants them. they are only 31.4 pointers, but with the new Core release version they go through my Barton at the rate of 12% finished per hour or FASTER-- seen the Barton do 16% of total WU an hour on one of them. I have had ZERO of the new semi-betas crash F@H client or the new core release.
Way to get new core release:
Pause or stop client.
wipe the file Core_78.
restart client.
It will very likely get new release of Core_78, which at last I heard was release version 1.55. It was tested with the version 4 client and client betas, very neat release for boht client and the new Core_78.
I will give you a sample of increase in throughput from the flags being active and the new core release-- The older core did about 3.5 31 pointers in a day. The new one averages 4.2 of same WU grade a day (24 hour time span), and in some cases same set of WUs. The Barton got a bunch of those, I kept logs. Barton old core release version, was running about 10-11 min per percent for Project 1000 WUs when stable and I was not playing with things trying to push the folding. New core release with new client, ALL switches active, about 8.5 to 9.8 min per percent-- varied some by machine load and WU. That took total WU complete time from 17-18 hours total, down to about 9-10 hours for the biggest WUs folding has ever sent out. Those are 50 pointers. Would you rather have actual pointage of about 90 points a day, or 130-140 per day average over long term out of your Barton????
That is why my two boxes, one P4, one Barton, got 1143 points last 7 days worth of computing (that is understated by stats mirror update lags right now, this week will have about 1260 points if things go smoothly in REAL local processing pointage-- for weekly production). New client, all switches, new core_78 release, rocking points. I OC 12% on Barton box (overall diff in clocking from base), about. CPU is at 2070 actual MHz, has been for 10 days, RAM is only pumped to 172 MHz base from 166 nominal-- an average Barton box, not an extreme box by any means, with GRAPHICAL client running on XP. I have not had to play with voltages much at all.
John.
If not wanting to jump, WADE first....
John.