Quota per CPU
17 Sep 2007 23:47:20 UTC
Topic 193151
(moderation:
Isnt this currently at a level which is ridiculous? Wouldnt it be better to reduce this in order to get rid of hosts that simply burn through their quota? My E6300 has 72 per core. Thats absurd considering current work units take longer than a day.
My 2 cents.
Quota per CPU
)
The only time it is a problem is when a bum machine errors out every result it tries, but in that case its quota gets knocked down quite quickly.
Too-low quotas have been a problem on Einstein in the past. I've not seen much damage from too-high quotas.
The current typical Work Unit length will be history in a week.
Allen bumped the quota first
)
Allen bumped the quota first to 64 and then to 72 after Core 2 Duos made their appearance on Einstein. Some WUs at the time were very short and it was pointed out that a Core 2 at high overclock could theoretically do more than 64 short WUs a day per core.
But why its still at 72, i have no idea, 16 would be overkill enough =)
Team Philippines
Resonably low WU quota is
)
Resonably low WU quota is good for both project and user.
It saves bandwidth for the first and trafic for the second in the case if something going wrong.
So it's parameter to change with CPU advance and app/WU crunch time modifications. If it setted too high it loses its meaning.
RE: RE: Isnt this
)
I agree w/Archae86. The message board used to be peppered with people begging for the quota to be raised and they provided lengthy dissertations on why, now are we going to extol the virtues of a low quota? You people are never happy. We don't even know what the WU lengths will be in the future over time; is Bruce Allen supposed to raise the quota one week just to lower it the following week? ...and that's my 2 cents.
RE: I agree w/Archae86.
)
Good point. Let's do the math:
As to future WU lengths, Bernd has stated that the S5R3 tasks will have an average length roughly the size of the smallest S5R2 units, which were less than one third of the current 650+ credits "monster" tasks. So a fast core can crunch 3 per day, maybe. Hopefully we will see some optimization of the client soon, this will hopefully double or tripple the speed => (say) 8 units per day. A 72 units per core&day quota would allow you to download 9 days of cache in a single session, which is one day below the max cache size. I think this would be adequate, and I can already hear people asking for more :-)
CU
H-BE