A strange problem.
Two ~identical machines gave almost identical benchmark results. Both are marked as "work" and both connect saying "may run out of work in 1.50 days". Yet one consistently asks for ~250,000 seconds of work and the other ~110,000. The former obviously gets twice as many WU's each time.
Not a big deal, but curious as to why.
G.

---

> A strange problem.
> Two ~identical machines gave almost identical benchmark results. Both are
> marked as "work" and both connect saying "may run out of work in 1.50 days".
> Yet one consistently asks for ~250,000 seconds of work and the other ~110,000.
> The former obviously gets twice as many WU's each time.
> Not a big deal, but curious as to why.
> G.


Hi Giles,

Run your benchmarks to see if they are close.
Check your individual settings for each unit.

Timmy

---

Could be many things. Check out the host page for each machine and see if the information being reported back to the server is the same. If by chance you had the preference for do no work while computer is in use and one of the machines was used more than the other, then it wouldn't request as much work as the other.

Also thrown into the mix is the amount of time in the "% of time client is on 73", "% of time host is connected 73", and "% of time user is active 73". that are listed in the computer summary information at the bottom.

If one machine is at 50% and the other in the high 90's, well, that is the difference. Those numbers shold adjust up and down over time with a decay function. In my own experience they usually settle into a fairly steady state value and do not seem to change much if at all.

The bottom line is that if you paly games, for example, on one machine and the other one mostly just crunches, there is the difference right there ....

---