I updated the scheduler so please post here if you are continuing to have issues with crazy cache sizes. The scheduler now uses the cpu run time preference as the estimated job duration when determining how many jobs to send to a host. Hopefully this should improve the job cache size.

---

I updated the scheduler so please post here if you are continuing to have issues with crazy cache sizes. The scheduler now uses the cpu run time preference as the estimated job duration when determining how many jobs to send to a host. Hopefully this should improve the job cache size.

Good to hear.
Thank you for your efforts.

---

Grant
Darwin NT

I doubt there was a sudden increase in the number of users signing up, so this graph shows just how bad the issue was.


Almost 600k more Tasks in progress than usual, over a 50% increase.
As tasks miss deadlines & get resent, over the next week or so the number should end up back around the 1 to 1.1 million mark.


The next new application release (or surge in new users) should result in a much smaller jump in In progress Tasks, and no mass missing of deadlines or Tasks being aborted.
Good for the project & good for the crunchers.

---

Grant
Darwin NT

Hopefully the updates I made fixed this issue. Thanks!

Edit: When I reattached, the appropriate amount of jobs were downloaded so that's a good sign.

---