| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Official Messages
Forum: News
Thread: 2023-07-31 Update (MCM1 issue resolved) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 74
|
|
| Author |
|
|
thunder7
Senior Cruncher Netherlands Joined: Mar 6, 2013 Post Count: 232 Status: Offline Project Badges: 
|
thunder7 said: So does anybody know where that irksome 1000 job limit is exactly in the source? My larger machine just can't download enough to keep being active over the (all too frequent) bumps in the road here. The last 55 jobs being crunched by 88 cpus all show a report deadline of August the 11th, 23:45, so it should be possible to download more and still return them on time. I feel I'm at a disadvantage with one big machine compared to many smaller ones, each downloading a 1000 jobs. There is MAX_WU_RESULTS (which is at 100?), SELECT_LIMIT, QUERY_LIMIT, MAX_JOBS, WF_MAX_RUNNABLE_JOBS, to name a few. I made an Issues thread on the official BOINC GitHub repository back in 2019. This might help, but I haven't thought about this in a few years. Improve logic behind WF_MAX_RUNNABLE_JOBS = 1000 There's also the official BOINC Message boards that are fairly active, and a lot of the core volunteer developers/founders are there too. To answer your question, I believe it's WF_MAX_RUNNABLE_JOBS, which must be a constant hard-coded to 1000 somewhere, so just changing that constant might be a workaround. It's not pretty, but neither is the original limit. [Edit: I'm not 100% sure if that's the constant that needs to be changed to be honest, so let us all know if you wanna build your own BOINC :) ] I can now confirm that chaning WF_MAX_RUNNABLE_JOBS works. I didn't get the Ubunu 22.04 package to compile cleanly from source, but it did make an executable, and it works: 3906: 15-Aug-2023 12:46:59 Reporting 2 completed tasks |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2171 Status: Recently Active Project Badges: 
|
Hi thunder7,
You gracefully copied from your Event Log: 3907: 15-Aug-2023 12:46:59 Not requesting tasks: too many runnable tasks (runnable 2003/2000) There it was, the 'too many runnable tasks' limit! You bumped into it, and I noticed one thing that was different from my (regular) version of BoincMgr: the number of tasks was added while my version (7.20.2) doesn't report that. Is that a new feature or did you add that to the code yourself? I'm asking just out of curiosity, although I think adding something like this would be worthwhile in a future version of BoincMgr. Adri |
||
|
|
thunder7
Senior Cruncher Netherlands Joined: Mar 6, 2013 Post Count: 232 Status: Offline Project Badges:
|
Hi Adri,
----------------------------------------I added that to the code myself, because I wanted to see what was happening - at first, nothing was changed. It turns out the ubuntu way of compiling source to package leaves a cache of unpacked sourcefiles in a location that I didn't know about (....dfsg/client directory), so I spent some time finding out why I didn't see anything happening. Now I'm glad it's in there, because it's also a clear visual indicator for when some upgrade will have replaced my executable. I do find it strange that this WF_MAX_RUNNABLE_TASKS is not the real limit, it's more like WF_MAX_RUNNABLE_TASK + (the amount of tasks we got last time). [Edit 1 times, last edit by thunder7 at Aug 16, 2023 4:15:58 PM] |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2171 Status: Recently Active Project Badges:
|
Hi thunder7,
----------------------------------------Now I'm glad it's in there, because it's also a clear visual indicator for when some upgrade will have replaced my executable. Indeed it is, good thinking!I don't know if you do, but I can always choose when to update and what to update, and I always look at what will be updated. So if there's a new Boinc version, it will not be missed when reviewing the updates. However, upgrading to a new release of your operating system is a different story, of course. I do find it strange that this WF_MAX_RUNNABLE_TASKS is not the real limit, it's more like WF_MAX_RUNNABLE_TASK + (the amount of tasks we got last time). That's a feature, we should be glad to be able to catch more tasks than possible and count our blessings.  When you look at it another way, it isn't that strange: if it wouldn't be possible, there wouldn't be any need for the 'too many runnable tasks' message.  Adri [Edit 1 times, last edit by adriverhoef at Aug 16, 2023 11:12:29 PM] |
||
|
|
|