On Sun, 30 Oct 2005 13:06:01 -0500, Magic User <magic@nowhere.com>
wrote:

On Sun, 30 Oct 2005 17:00:11 GMT, Martin 53N 1W
<ml_news@ddnospamddml1dd.co.uk.dd> wrote:

John wrote:
[---]

I think to only time the 14 day time limit is exceeded is if you have 10
days worth and crunching takes longer. However, I think this is likely
to be a very minor problem. This can be overcome by asking for a few
days less cache.

If you are caching WUs because you are worried about Berkeley being 
offline, you should be EQUALLY WORRIED about uploading the results in 
time...

Hence, a WU cache + WU complete time that is greater than 7 days looks 
to be silly. Also, a large cache delays adding up the credits for everyone.


Happy crunchin',
Martin

After reading this thread I decided to check my average turn around
time which turns out to be about 4.5 days. This seems odd since
I have the WU cache set to 7 days in my seti preferences!

Magic

Yes the cache to real time is not very accurate. That is why Berkeley
allows such a setting. The problems lie in the fact that when your
machine is benchmarked the benchmark is so small that it can't be
accurate over the life of a workunit. So it is a guesstimate, these
are often wrong and Berkeley is working on a way to make them closer
to real life. The problems lie in that we users often turn everything
off and just let the benchmarks run when we see them. This often is
not real life for the machine, causing problems. The later versions of
the program are better but still will never be totally accurate due to
benchmarking. The newer versions are working towards using crunched
workunits as benchmarks of how long it takes your machine to crunch a
unit, it is trying to learn as it goes. This is not up to snuff yet
either.