Having a Ryzen that runs a tad over 4GHz as expected, tasks finish a lot faster than on an old core2 duo. What I had not expected is that when uploading tasks web pages time out in my browser and on other half's computer. Limiting upload rate to 40KB/second resolves this.

What I don't understand is why this doesn't happen on my laptop and didn't happen with the core2duo as upload rates then were the same.

My bored band is rather slow with upload rate maxing at about 100KB/s when not limited.

Upload pipes are traditionally a lot smaller than download pipes in most network connections. Plus, you are using different hardware than your laptop so likely the internet chipset is different and most likely needs some tuning compared to your laptop.

You can control the max number of connections that BOINC uses and also control the maximum number of tasks to report at once with settings in the cc_config.xml file.

You might change <max_tasks_reported>N</max_tasks_reported> to <max_tasks_reported>1</max_tasks_reported>
to prevent BOINC from hogging your bandwidth and preventing web pages from loading.

Thank you Keith - you taught me a bit of theory that I needed to confirm operations.

I ran into the same issue and changed my max tasks reported to 2 and cured my problem (guess work until now).

Tim

---

You might change <max_tasks_reported>N</max_tasks_reported> to <max_tasks_reported>1</max_tasks_reported>
to prevent BOINC from hogging your bandwidth and preventing web pages from loading.

Nice, but reporting doesn't use bandwidth like uploading does. And uploading can be curtailed, just as downloading, via the preferences: Options->Computing preferences->Network->Limit download rate and limit upload rate.

Uploading moves a physical file from your hard drive to a hard drive at the server. Depending on the size of this file and the speed of the user's internet and that of the project, this can take absolute ages.
Reporting tells the server's database what the outcome of the task was. If one reports several tens or hundreds of tasks at the same time this may be problematic for the server's database to accept, especially when lots of other computers try this at the same time as well. The size of the report file may then be in the mere tens of megabytes, but the file itself isn't uploaded (as in moved from your hard drive to the server's hard drive), only its contents are sent directly to the database.

I've had connection problems in the past, usually because I had two computers on the network with P2P software open which both opened a mass of ports, as each connection uses its own port. The fix here was to decrease the amount of connections each P2P client was allowed to use.

---

In my case it is the uploading files that is the problem. Even with just one task uploading files the problem occurs and having limited the upload rate to 75% of my maximum speed seems to have cured the problem. It just seemed strange to me when even if my old desktop and the laptop were both uploading at once I had no issues.

Probably not worth going over to git-hub and requesting a feature that monitors other programs wanting to access the internet and automagically throttling the upload speed!