Wouldn't this require the box running dry on a semiregular basis? Otherwise the 1st time it runs dry Rosetta will be well over it's share of CPU time, and unless another dry spell strikes will not get any cycles for a very long time. One 8 hour block of Rosetta will take 33days of 100% alberting before it resumes running.
That's the point - if Einstein is dry, you'd run Rosetta; otherwise, you'd run roughly 1 Rosetta WU per month. The scheduler won't let you return the work past deadline, so all would be well. (Although I can see where if you have a large cache, it could be a problem.)
_My_ preference is for the "backup" project to have at least a 10% share, that way you work on it at least a couple of times each day. And while CPDN WUs "last forever" and from that viewpoint make a good backup, the _last_ thing you want to do is get in deadline trouble with a 1-year result, so if CPDN is the backup, I prefer it to get at least 20-25%.
My point is that if einstien doesn't run dry for a month after doing so you'd have a Rosetta WU that never gets completed. My objection is to taking work that there's a reasonable potential you won't complete ever, thus causing problems for the ohter project. At 10% like you suggest that's unlikely to be an issue.
My point is that if einstien doesn't run dry for a month after doing so you'd have a Rosetta WU that never gets completed. My objection is to taking work that there's a reasonable potential you won't complete ever, thus causing problems for the ohter project. At 10% like you suggest that's unlikely to be an issue.
It will be done because you will enter EDF and finish off the work pending. Then not pull any unless you ran out of EAH work.
If I was not doing such a high percentage of EAH work for personal reasons this for me would be a non-issue. It is just that there are some that are single project minded and if there is no good reason not to, upping the quota a little more is not a huge deal.
If the 1 hour work units are an anomaly, then the quota is fine as it stands, or even high ...
My point is that if einstien doesn't run dry for a month after doing so you'd have a Rosetta WU that never gets completed. My objection is to taking work that there's a reasonable potential you won't complete ever, thus causing problems for the ohter project. At 10% like you suggest that's unlikely to be an issue.
It will be done because you will enter EDF and finish off the work pending. Then not pull any unless you ran out of EAH work.
As I said - the scheduler won't let you miss the deadline. :-)
Quote:
If I was not doing such a high percentage of EAH work for personal reasons this for me would be a non-issue.
Hm... I'm doing the same, for the same reason, but I have slower hosts. I haven't hit the quota problem yet. :-)
RE: RE: Wouldn't this
)
My point is that if einstien doesn't run dry for a month after doing so you'd have a Rosetta WU that never gets completed. My objection is to taking work that there's a reasonable potential you won't complete ever, thus causing problems for the ohter project. At 10% like you suggest that's unlikely to be an issue.
RE: My point is that if
)
It will be done because you will enter EDF and finish off the work pending. Then not pull any unless you ran out of EAH work.
If I was not doing such a high percentage of EAH work for personal reasons this for me would be a non-issue. It is just that there are some that are single project minded and if there is no good reason not to, upping the quota a little more is not a huge deal.
If the 1 hour work units are an anomaly, then the quota is fine as it stands, or even high ...
RE: RE: My point is that
)
As I said - the scheduler won't let you miss the deadline. :-)
Hm... I'm doing the same, for the same reason, but I have slower hosts. I haven't hit the quota problem yet. :-)