Tazz wrote:

OK, I have BOINC set up to store between 3 and 4 days worth of WUs (24
hrs. x 4 days = 96 hrs.) BOINC requests 270862 seconds of WUs (270862
sec / 60 = 4514.3666 min. / 60 = 75 hrs.), this ended up being 5 WUs
that show 18:17:30 per WU to completion (18 hrs. x 5 WUs = 90 hrs.)

This is all fine and good, but it REALLY only takes about 2 hrs. 30
min. to complete one WU. So my 4 day cache is only lasting about 12
hrs. 30 min.

I've run the benchmarks countless times but nothing seems to change
this. The way it is now, I'll have to set my cache between 39 and 40
days to get enough WUs to REALLY last 4 days.

Please, if my reasoning is pure BS, then someone show me how this
works.

Something strange is happening at Berkeley. WUs are showing up as taking
approxiamtely six times longer than they actually take. AFAICT this started
on the 10th, all was well before that. Obviously this bug makes a mockery of
the cache size system as it's calculating that the units are going to take
six times longer than they actually do, so you're only getting one-sixth of
the units you should get.

I suggest leaving things as they are for now and just letting your machine
get units as it needs them. If you set your cache for 40 days and it gets
fixed you're going to have a whole bunch of units that aren't going to get
crunched before they expire, making the whole crediting system a mess.
--
~misfit~