Normal F@H behaviour?

[oceaness]

Just a quick question: Is it normal that F@H starts quick and slows down...

i.e.
When I started this current WU it was doing one frame every 15 seconds, now it's down to one frame every 37 seconds, which when you consider the total frames is a hell of a slow down:

15*10,000 = 1.7 days
37*10,000 = 4.2 days

 

[BillytheImpaler]

I'd consider it normal. In the beginning it was doing some easy calculations that your CPU was good at crunching. Later in the simulation it ran into a bit that took a bit more work and as such it took longer. It's also possible that during that period something else was stealing CPU cycles. You'd be suprised what can nick cycles away from DC apps.

 

[oceaness]

After restarting the PC and resuming the work unit it's now on 16 seconds per frame. Theres something funny going on. Estimated time is now 1day 13hours rather than the 3days 18hours it was yesterday.

May possibly be that my watercooling control software was nicking some CPU, have closed it and will now see what happens to the seconds per frame.

 

[rich99million]

are you using the graphical version?

if so i wouldn't take much notice of the estimated time if i were you as it's famously unreliable

fahmon is better or EMIII if you are really bothered by it

 

[oceaness]

Not really bothered now it's going at 16s per frame.
It's staying at 16 seconds a frame as well thats whats important.
Guess it was WaterChill Control Panel stealing CPU cycles.

I am running the graphical client until this WU is done then switching to the CL client
I know I could switch and carry on processing this WU but I'm lazy so I'll just wait till it finishes and sends it off.

Thx for the replys guys