Forum > Windows
Can someone confirm this?
Fredericx51:
--- Quote ---Not to us, that's the server log and unchanged in that regard. The change should avoid the "reached max..." message in most cases, but it'll be the unscaled max_jobs_per_day when shown.
Joe
--- End quote ---
When taking GPU's into Quota-##, is an average taken, since the big differences between 'older' and 'latest' or FERMI GPU's capabilities and Compute Power. (ATI-GPU's, too ofcoarse)
Or by the (G)FLOPS ##, estimated by BOINC (6.10..56)?
Josef W. Segur:
--- Quote from: Fredericx51 on 16 Jun 2010, 06:57:18 am ---When taking GPU's into Quota-##, is an average taken, since the big differences between 'older' and 'latest' or FERMI GPU's capabilities and Compute Power. (ATI-GPU's, too ofcoarse)
Or by the (G)FLOPS ##, estimated by BOINC (6.10..56)?
--- End quote ---
Quota is meant to protect the project from a host which has gone bad, and is the same no matter what the speed of the crunching resource. The slowest CPUs with about 40 Whetstone MIPS have the same 100 basic quota as the fastest. Same goes for GPUs, with the change yesterday they should be back to all having a basic quota of 500. Even the slowest GPUs can trash that many very quickly if they go bad.
The project's config.xml specifies the 100 basic quota and the 5 multiplier for GPUs. They don't want hosts to run out of work if the host is producing good results, if necessary they may increase those settings. But they won't set them so high that the protection is ineffective.
Joe
Navigation
[0] Message Index
[*] Previous page
Go to full version