Message boards : News : More tasks per thread: about a day of work in your queue
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 23 Sep 26 Posts: 242 Credit: 54,980,907 RAC: 1,491,573 |
As promised in the forum, we've raised the number of tasks each computer can hold: up to 30 tasks in progress per CPU thread (it was 2 a few days ago, then 4). With tasks of about an hour, that's roughly one day of work per thread. Your computers can keep crunching through a network outage, a server maintenance, or while your client spends time on other projects. To benefit from it, your BOINC client must also ask for that much work. In Options → Computing preferences → Network, raise "Store at least … days of work" and/or "Store up to an additional … days of work" (for example 1 day). The client never fetches more than these settings allow. A few more notes: Tasks still have a 7-day deadline, so a one-day queue leaves plenty of margin. The server keeps a large reserve of ready tasks and refills it automatically. The limit is per thread: a 32-thread machine can hold up to 960 tasks. Thanks to everyone who asked for this, and happy crunching! |
|
Send message Joined: 27 Sep 26 Posts: 42 Credit: 141,621,123 RAC: 4,172,786 |
Awesome, thank you. Woo also a 465 board. |
|
Send message Joined: 28 Sep 26 Posts: 17 Credit: 15,948,746 RAC: 194,165 |
In reply to benjamin's message of 12 Oct 2026: As promised in the forum, we've raised the number of tasks each computer can hold: up to 30 tasks in progress per CPU thread (it was 2 a few days ago, then 4). With tasks of about an hour, that's roughly one day of work per thread. Your computers can keep crunching through a network outage, a server maintenance, or while your client spends time on other projects. For host running cpu task only, did you switch back to a max of 4 tasks per thread instead of the 30 tasks/thread? |
rebirtherSend message Joined: 24 Sep 26 Posts: 29 Credit: 39,233 RAC: 755 |
Check in your account prefs Max # of jobs for this project |
|
Send message Joined: 23 Sep 26 Posts: 242 Credit: 54,980,907 RAC: 1,491,573 |
In reply to rebirther's message of 26 Oct 2026: Check in your account prefs Thanks rebirther, that's a good first thing to check. In your case, though, pututu, your "Max # of jobs" preference is set to no limit, so you were right: the server had been lowered to 4 tasks in progress per CPU thread while we prepared the GPU opening. We've just raised it to 12 tasks per CPU thread. With tasks of about an hour, that's roughly half a day of work in your queue. It's a balance: enough buffer to ride out a short server hiccup, while keeping the work spread across everyone now that many new computers are joining. |
|
Send message Joined: 28 Sep 26 Posts: 17 Credit: 15,948,746 RAC: 194,165 |
In reply to benjamin's message of 26 Oct 2026: the server had been lowered to 4 tasks in progress per CPU thread while we prepared the GPU opening. We've just raised it to 12 tasks per CPU thread. Thanks. 12 tasks/thread is better than 4 tasks/thread. 4 tasks/thread might be a problem if my internet has temporary connection issue or server is unreachable and get a message like "next project project update in xx:xx hours" rather than the default 60 seconds delay. |
|
Send message Joined: 27 Sep 26 Posts: 21 Credit: 27,740,877 RAC: 219,288 |
In terms of the way boinc is run, it is better to allow a lot of tasks to be downloaded at the users request and not limited by the server if the server can handle the load. If a user doesn't want so many tasks they need to set the boinc preferences to fewer tasks: computing/general/"store at least n days and up to an additional m days or work" Having the "Max # of jobs for this project" project preference is always good. :thumbs up: However setting the max number of threads able to be downloaded from the server side based on a few users' request and needs is not good as it may limit other users based on their needs. This is true if people want to download a larger number of tasks to cover an extended outage from a communications provider for instance. Also limiting the number of downloads interfere with users' bunkering tasks for various boinc competitions and challenges. |
|
Send message Joined: 23 Sep 26 Posts: 242 Credit: 54,980,907 RAC: 1,491,573 |
@pututu: exactly, that was the concern with 4 per thread. 12 gives a comfortable margin for a short connection or server hiccup. @Werinbert: fair points, and I agree in principle that the client's own cache settings should normally decide. The server-side limit isn't based on a few users' requests: it's there to keep the work spread fairly while many new computers are joining at once, and to keep results coming back quickly, because they feed the selection of the next search areas. With tasks of about an hour, 12 per thread is roughly half a day of buffer. The "Max # of jobs" preference stays available for anyone who wants fewer. We'll revisit the limit as the server capacity grows. |
