Posts by tangofan

InfoMessage
1) Message boards : BOINC Manager : Feature Request: Provide statistics for network usage per project in BOINC Manager
Message 111094
Posted 18 Feb 2023 by tangofan
git-hub is the place where you can request a feature. You will need to create an account there. Developers don't frequent this forum much or if they do, they don't make it evident by posting.

Edit: The recent OIFS tasks at climateprediction.net could easily go over that limit in a day or two on a multi-core system. (About 1.8GB per task and on a fast machine under 5 hours to completion.)


Thank you,I've submitted a a feature request on github: https://github.com/BOINC/boinc/issues/5105

Re. climateprediction: If they use that much network data in relation to the CPU time they need, then this wouldn't be a good project for me. I'm generally looking for projects that use more CPU time in relation to network data usage.
2) Message boards : BOINC Manager : Feature Request: Provide statistics for network usage per project in BOINC Manager
Message 111085
Posted 16 Feb 2023 by tangofan
Not sure, if this is the right board for this, but here we go:

I'm running the BOINC Manager under Windows 10 x64 21H2. Overall BOINC Manager has very good statistics for CPU/GPU usage (tab "Statistics") and for disk usage (tab "Disk") per project, but there is zero information on network usage.

Since my internet provider has a data cap implemented, I gave BOINC a limited network usage allowance and set it to 32GB every 30 days. To my great surprise that allowance was exhausted after only 13 days. Unfortunately there is no obvious way of finding out which projects are responsible for using up the bulk of that allowance.

Thus I suggest that in addition to "Statistics" and "Disk" another tab (working name "Network") should be implemented and that tab shows the network usage per project for the current host. This could be done as a rolling average over different time periods, e.g. 3, 7, 14 and 30 days.


Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.