My perception is that you wish to crunch Seti mainly and would like to have E@H there as a backup in case of a really bad Seti outage. You don't really want a low cache because E@H might "take over" and get extra share during Seti outages. With JM7's work as I understand it, if this were to happen, Seti will accumulate a "debt" and will get extra share once it's back on line and your resource share wishes will eventually be honoured in the longer term. All of this with added protection against any work exceeding the deadlinne.
Top man, yes that is what my aim is. Seti@home has 66% share and Einstein 33% share. Einstein is there in part as a reserve for the outages on the Seti@home project.
I've left in the lines that represent your real "problem". With E@H 7 day deadline, it's not wise to set a 6 day queue.
The problem I have is that seti@home gets the estimate of how long a WU will take very wrong, WUs take approx 3 hours but Boinc manager estimates them at 6.5 hours so when I set a 6 day cache it is in practice a 3 day cache for Seti@home. To prevent einstein@home running past the deadline I have left four einstein workunits permanently in suspended status so that einstein has in fact only one WU in its cache. It was the only way I could think of to try and balance having a reasonable seti@home cache and keep einstein@home within the short reporting deadlines. Looks like this idea did not work out as when it defers for 24 hours the completed WU is not reported back until this deferred period is completed.
I will install the new version of Boinc manager when it is released. I guess what I am really after is the ability to set different cache sizes for different projects.
My perception is that you
)
My perception is that you wish to crunch Seti mainly and would like to have E@H there as a backup in case of a really bad Seti outage. You don't really want a low cache because E@H might "take over" and get extra share during Seti outages. With JM7's work as I understand it, if this were to happen, Seti will accumulate a "debt" and will get extra share once it's back on line and your resource share wishes will eventually be honoured in the longer term. All of this with added protection against any work exceeding the deadlinne.
Top man, yes that is what my aim is. Seti@home has 66% share and Einstein 33% share. Einstein is there in part as a reserve for the outages on the Seti@home project.
I've left in the lines that represent your real "problem". With E@H 7 day deadline, it's not wise to set a 6 day queue.
The problem I have is that seti@home gets the estimate of how long a WU will take very wrong, WUs take approx 3 hours but Boinc manager estimates them at 6.5 hours so when I set a 6 day cache it is in practice a 3 day cache for Seti@home. To prevent einstein@home running past the deadline I have left four einstein workunits permanently in suspended status so that einstein has in fact only one WU in its cache. It was the only way I could think of to try and balance having a reasonable seti@home cache and keep einstein@home within the short reporting deadlines. Looks like this idea did not work out as when it defers for 24 hours the completed WU is not reported back until this deferred period is completed.
I will install the new version of Boinc manager when it is released. I guess what I am really after is the ability to set different cache sizes for different projects.
Many thanks for all the help. :-)