long workunits for optimized clients by akofs
Anonymous
8 Apr 2006 8:40:32 UTC
Topic 13311
(moderation:
Do you have any idea how the scheduler should tell "akofs optimized clients" from our ordinary Apps?
BM
long workunits for optimized clients by akofs
)
Thanks for the Hint.
The stderr output is kept as a text blob just for debugging purposes; grepping over the blobs would be too expensive, and associating them with a host would require altering the db schema (host table), not to speak about the effort needed to code this into the various BOINC server components (and debug...) - no way.
I think that when the servers are ready to handle a graater load and we publish faster official Apps, we will also raise the daily quota again (which we already did).
Until then I'd rather encouage you to attach to another BOINC project as a backup if you don't want to have your computer cycles unused.
BM
BM
First: there's almost nothing
)
First: there's almost nothing that's impossible, it's just a matter of effort one puts into it. However, in the real world, everything is limited - like the manpower of this project.
The only thing that looks remotely sane to me is having the workunits linked to the amount of work that is requested, i.e. the more work the client requests at once, the more likely it is to be given larger workunits. This should in principle give the larger chunks of work to the faster Apps (in the long term).
However this would require to rewrite and replace at least the scheduler in the middle of a run. which is rather risky (to say the least). Honestly I wouldn't want to put the stability of the project at stake for that. I'm rather against fixing something that isn't broken.
BM
BM