General observation

zagadka
zagadka
Joined: 29 Apr 06
Posts: 12
Credit: 17088
RAC: 0
Topic 191198

I have noticed that without changing anything that it slowly takes longer and longer time to process a WU, from just over 2.6k secs to over 4.1k secs. The WUs my computer has been working on during this has only been z1_1052 WUs.

Has anybody else noticed a similar trend or should I look for the cause elsewhere?

Alinator
Alinator
Joined: 8 May 05
Posts: 927
Credit: 9352143
RAC: 0

General observation

Quote:

I have noticed that without changing anything that it slowly takes longer and longer time to process a WU, from just over 2.6k secs to over 4.1k secs. The WUs my computer has been working on during this has only been z1_1052 WUs.

Has anybody else noticed a similar trend or should I look for the cause elsewhere?

I did a cursory examination of your results and think you'll find the real CPU time used is pretty consistent at around 3200 seconds (at least on the 58 or so still showing).

The variation in the reported CPU time is an effect from using Trux' Calibrating Client, and is normal.

HTH,

Alinator

zagadka
zagadka
Joined: 29 Apr 06
Posts: 12
Credit: 17088
RAC: 0

RE: RE: I have noticed

Message 30821 in response to message 30820

Quote:
Quote:

I have noticed that without changing anything that it slowly takes longer and longer time to process a WU, from just over 2.6k secs to over 4.1k secs. The WUs my computer has been working on during this has only been z1_1052 WUs.

Has anybody else noticed a similar trend or should I look for the cause elsewhere?

I did a cursory examination of your results and think you'll find the real CPU time used is pretty consistent at around 3200 seconds (at least on the 58 or so still showing).

The variation in the reported CPU time is an effect from using Trux' Calibrating Client, and is normal.

HTH,

Alinator

Thanks for the explanation :)

There is another pattern, that actually gives away that it is the calibrating client that has caused this effect. The WU before the one reported at 2.6k secs is actually the first one that the client has adjusted the claim for.

Dave Burbank
Dave Burbank
Joined: 30 Jan 06
Posts: 275
Credit: 1548376
RAC: 0

RE: There is another

Message 30822 in response to message 30821

Quote:

There is another pattern, that actually gives away that it is the calibrating client that has caused this effect. The WU before the one reported at 2.6k secs is actually the first one that the client has adjusted the claim for.

Trux usually takes about 30 WUs before the credit calibration stabilizes,
you should see credit claims around 35 cobblestones now.

There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.