Strange goings on with 1662

Associate
Joined
21 Jan 2005
Posts
762
Location
Manchester
Got this on my main machine, nice methinks, until it told me it was going to take 10 days, bugger methinks.

Anyhow I'm running this through the machine in my sig which I had clocked down to 2.7 during the hot weather, now that its cooled I up the clock to 2.75 11x250 and hey presto its now gone down to 2 days.

This is strange, so I go back to 2.7 and open f@h and its back to 10 days.

Very odd that a 3% clock increase can give a 500% increase in F@H performance on this WU.
 
let me guess - you're using the Graphical version and the ETA is totally unreliable?


try FahMon - it's a lot more reliable in terms of a meaningful ETA and will also keep score of what PPD (points per day) you've managed with each different project on your machine


you can also use it to monitor machines accross a network - handy :)


edit: fully illustrated setup guide here
 
Yeah, Rich has got it. The graphical client's ETAs aren't too accurate at the best of times, but they're especially bad when the client has just been opened. The ETA went back to 10 days because you'd just opened the client!

It's best to change to the console client and use FAHMon - not only will you get more accurate estimates but the graphical client has a few annoying bugs in it which you're best off without.

If you want to stick with the graphical client, though, don't listen to its estimates until it's been open an hour or two.

Oh and don't have the graphics running when the WU finishes or it will probably crash ;)
 
Back
Top Bottom