I wouldn't blame the scheduler exactly for having problem with multiple WU types. More that its decision time for allocating tasks increases under high server loads causes timeouts - http or data reads.

Also it seems to have a load watchdog, where as now, it likes to only give 1 task at a time per computer thread for downloads. Likely due to too many dropped calls to it.

I remember not too long ago seeing return rates upward of 180-190k per hour during an Overflow storm. This was with Full services running, i.e. Scheduler, Uploads and Downloads with the only problem being the splitters couldn't keep up. Recent problems have happened with a Much lower Return Rate and even though the Scheduler and Download services were Stopped once the problem began. Once the Problem begins Most of the Server Load Stops, but the problem persists. Big difference there. Past test show No problem with High Server Loads as long as there is just One Type of Task in the Cache. Past tests show the problem only happens when more than One type of task is in the cache. Those tests are why we are now running Arecibo VLARs on the GPUs, the problem started when the Arecibo splitting began.

BOINC is temporarily shut down for maintenance. Please try again later.

DA must have been inspired by yesterday's outrage here.

---

115 is here

https://setiathome.berkeley.edu/forum_thread.php?id=83895