Just two things to mention: Doubling the deadline means basically doubling the size of our database, and it means that people have to wait for their results to be validated and thus credit granted potentially twice as long.
A deadline that depends on the "size" (i.e. expected run-time, credit etc.) of the workunit would be an interesting idea. I'll discuss that with the team.
BM

Petition - Deadline Relief for Longest Results
)
The deadline (actually its "length") is a property of the workunit and thus inserted by the workunit generator at time of creating the workunit, nothing is known (and necessary to know) about the host they will later be assigned to. The workunit generator, however, knows about the "size" of a workunit that is reflected by the number of credits that will finally be granted for it. A variable deadline would be derived from this "size" of the workunit, not from any info about any host.
Would this concept of a variable deadline be desirable?
BM
BM
RE: RE: The other thing
)
I think so, but even more important is that it also requires a newer "minimal" Client version. We're still issuing work for all Clients from version 4.19 on, and I don't intend to change this without need.
Another aspect is that this way the computation time spent on the canceled result is alway wasted (does the participant get credit for it anyway?). My guess would be that while this gives faster results for the project and faster credit for the fast participants the waste of computing power is larger than what is lost by results arriving too late in the current scheme.
BM
BM
RE: RE: This has only
)
Let me just emphasize what I wrote in the original "S5R2" posting:
If an analysis of the S4 data took a year, analyzing twice as much data would have taken about 64 years with the old program (and the same computing power). The new program should basically be able to do this in about a year again (actually less, but we have more than twice the data). So it's about fair to say that the new program does the same work 64 times faster than the old.
BM
BM
We just started a new
)
We just started a new workunit generator with "dynamic deadlines". The deadlines of workunits generated from now on will vary between two and three weeks depending on the size of the wokunit (i.e. the number of templates within it, which should be proportional to the credit granted).
We'll watch it for a while, maybe we need to adjust the actual numbers.
BM
BM
RE: Bernd Machenschalk I am
)
So the right address would probably be Bruce Allen and David Hammer.
I'll forward the request to them.
In the longer run after upgrading our backend to newer BOINC you should be able to solve this problem yourself, but I don't know for when such an upgrade is scheduled.
BM
BM
Unfortunately the change only
)
Unfortunately the change only affects the newly generated workunits, older ones will still keep the old deadline. Feel free to abort the Task if you feel you can't meet the deadline.
(Gary, I'd like to contact you individually. I wrote two messages to the eMail address you registered here. Did you get them?)
BM
BM