Can someone confirm this?

[Fredericx51]

Sorry, I've posted a Out Off Topic   

My WIN XP64 CUDA (2x GTS250) host received only a few, probably Einstein was ahead, LTD, IMO.
And my ATI host received lots of CUDA compute capable MB WU's, which are now done by Q6600 CPU.
But the host did receive ~40, maybe some more, AP WU's, which is absolutely fabulous, for testing and
processing these, cause SETI MB (Optimized SSSE3), Docking, MW and Leiden, are running together.
Collatz C. is still on n.n.tasks.
Will do a test, offline, with a few AP & CC  WU's.

AP WU's are running OK, taking 2.5 - 5.5 hours runtime.

[sunu]

I'm not seeing this. Since this saga began, my pc downloads 100 or so workunits every day and then stops with quota reached.

That's interesting. What version, exactly, is it downloading for? (stock/anon, OS, platform, bits - anything you can thnk of).

I see this on my linux machine with AKv8 and crunc3r's cuda app. Of course fully anon platform. And I think I see this also on my other winxp machine with gtx470 running jason's x19, again fully anon platform. And I get, in both of them, the stupid message about non usable app_info.xml.

Another strange thing is that the message says about a quota of 100 tasks while on Berkeley's pages the linux machine says a quota of 64/day and the winxp machine 97/day.

[Richard Haselgrove]

I see this on my linux machine with AKv8 and crunc3r's cuda app. Of course fully anon platform. And I think I see this also on my other winxp machine with gtx470 running jason's x19, again fully anon platform. And I get, in both of them, the stupid message about non usable app_info.xml.

I've got no point of comparison for the Linux platform. But the WinXP, if confirmed, would contradict my observation, and hence destroy the hypothesis. Could you possibly confirm when you first reached the '100 quota' message?

Another strange thing is that the message says about a quota of 100 tasks while on Berkeley's pages the linux machine says a quota of 64/day and the winxp machine 97/day.

This one, at least, is easy. Beta also showed the obsolete version of the quota until I complained to DA, and he (very quickly) knocked up the replacement 'Application Info' pages for Beta. They just haven't migrated across to the main project yet - unless they appear after the outage.

[sunu]

I've got no point of comparison for the Linux platform. But the WinXP, if confirmed, would contradict my observation, and hence destroy the hypothesis. Could you possibly confirm when you first reached the '100 quota' message?

I don't remember exactly, I guess the first day the crappy server code was on? A gtx 470 burns more than 100 workunits a day.

[sunu]

This picture is from today. It got 100 tasks and then the usual, by now, reached 100 tasks quota message.

[Richard Haselgrove]

This picture is from today. It got 100 tasks and then the usual, by now, reached 100 tasks quota message.

What's more interesting is that it got the '100 tasks quota' message at 09:58:57, and then got new tasks at 10:00:27.

What's your time-zone - what's that in UTC?

[sunu]

It's UTC+3 You'll also see that before 10:00 it says quota of 85 tasks. The picture doesn't show it but after the downloads the quota went back to 100.

[Claggy]

Looks like there's been further changes: Changeset 21753

Timestamp: 06/15/10 15:21:57 (less than one hour ago)
Author: davea
Message: - scheduler: restore scaling of daily quota by # processors


and/or config.gpu_multiplier


- client: msg tweak


Claggy

[Richard Haselgrove]

Ah - "[version] [AV#%d] daily quota exceeded\n", av.id

That'll be useful.

[Josef W. Segur]

Ah - "[version] [AV#%d] daily quota exceeded\n", av.id

That'll be useful.

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

[Fredericx51]

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

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]

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)?

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