Lately the Scheduler appears to be having major problems whenever there is heavier than usual network traffic. The usual response to reporting or requesting work is "Scheduler request failed: Timeout was reached".

Routing the Scheduler traffic to the campus network (the one used by the web site & forums) may help with this issue.
At it's heaviest, inbound traffic is around 20Mb/s. During the outages when the Scheduler is down, but uploads are still possible the inbound traffic is generally around 8Mb/s.
So that would shift roughly 12MB/s of traffic from the present saturated link, it wouldn't overwhelm the campus network, & it would allow people to report & at least get new work allocated without difficulty.

---

Grant
Darwin NT

Lately the Scheduler appears to be having major problems whenever there is heavier than usual network traffic. The usual response to reporting or requesting work is "Scheduler request failed: Timeout was reached".

Routing the Scheduler traffic to the campus network (the one used by the web site & forums) may help with this issue.
At it's heaviest, inbound traffic is around 20Mb/s. During the outages when the Scheduler is down, but uploads are still possible the inbound traffic is generally around 8Mb/s.
So that would shift roughly 12MB/s of traffic from the present saturated link, it wouldn't overwhelm the campus network, & it would allow people to report & at least get new work allocated without difficulty.

Not allowed by the campus.

---

BOINC WIKI

That's a shame.
I don't think the issue is bandwidth related- there have been many times in the past where it has been impossible to download work due to network congestion, but you were still able to report & be allocated new work regardless of how bad the downloads were.
But moving the scheduler traffic to a different network from the download traffic would have shown one way or the other if it was network load related or sever load related.

---

Grant
Darwin NT