This is wierd...

SiriusB

SiriusB

SiriusB

Soldato
Joined
16 Dec 2005
Posts
14,443
Location
Manchester
I have two 116 point WUs crunching away at the moment.

One I started yesteday, and one I started earlier on today. The project numbers are 1718 and 1717 respectively.

Now, the 1718 project which has been running for over 24 hours already is at 50% and has another 24 hours to go...

The 1717 project on the other hand is at 5% and has less than 20 hours to go...

What gives? These are two very similar projects, at least points-wise, but one is taking twice as long as the other :confused:

SiriusB
 
They're on the same rig - 4400+ @ 2.6GHz and 2GB RAM

I have been playing games again this last few days since I borrowed COD2 off a mate but I doubt this would cause a WU to take twice as long - especially given my rig is on 24/7

SiriusB
 
I know it can all but stop a WU from crunching while you are gaming, but I don't see how a total of about 5 hours gaming in the last two days can increase a WUs ETA by a whole day.

If it said ETA: 24 hours before playing and still said 24 hours when I finished, then fine - I lost xxx number of hours to gaming...

However, I am in the situation where a WU appears to be taking an extra 24 hours even though at most 5 hours have been lost to gaming.

SiriusB
 
Okay just had at a look at my F@H log and it is running the WU with standard loops... the usual SSE Boost entry is not their either.

Okay, so it seems it is doing this WU the old fashioned way... question now is why :|

SiriusB
 
Okay so far so good, the log says SSE Boost OK... should know pretty soon if the 20+ hour ETA is shortened somewhat.

Still curious as to why it decided it wouldn't bother with optimisations when it started lol

EDIT: Ah, just spotted your post rich. I think I did see an improper shutdown entry in the log. Probably explains it :)

SiriusB
 
You must log in or register to reply here.
Back
Top Bottom