Posts by rilian

1) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2256) Posted 23 days ago by rilian Post: Hello! :) Presumably, BOINC should balance everything after gathering statistics for tasks calculations. Give it one or two weeks of work. hi @hoarfrost In theory yes, but this incident happened on "old" computer that crunched Sidock for more than a month. I had to manually set nomorework, allowmorework all the time. All projects on that computer have the same resource share. There is no way that computer could crunch 28 tasks with 8 cores in time.. This bug probably comes from server info which thinks that task average time is 31 hour (from server status page): CurieMarieDock 0.2.0 long tasks 14282 24846 [b]31.49[/b] (0.62 - 320.84) - Anyways, would it be possible to enable the setting to limit max number of jobs on server side? As I explained, because Sidock has very long tasks, this puts all other projects at risk of missing deadlines and missing credits Thank you!
2) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2253) Posted 24 days ago by rilian Post: with the setting above, my 8-core computer just got 28 long sidock tasks while there was a limit to cache 0.8 days :( i'm going to set this project no more work until admin would implement a max jobs limit setting to avoid losing the work in other projects UPDATE: i realized that this was a linuz computer without boinc 8.0.0 . For now i set "nomorework" on it for Sidock, and will experiment later The other computer with boinc 8.0.0 still crunches through 2 sidock tasks and i set the app_config setting to keep it 2. I will report once it will finish crunching and get new work
3) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2252) Posted 26 days ago by rilian Post: I have added app_config.xml to sidock project folder <app_config> <app> <name>cmdock-l</name> <max_concurrent>1</max_concurrent> </app> </app_config> Will report later if this helped ..
4) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2249) Posted 26 days ago by rilian Post: Note that the <max_concurrent> tag in the app_config.xml file sets the maximum number of tasks of a specific application to run at a given time. It does not control the work cache size, meaning if you set the max_concurrent to "2" say, it will download tasks to fill whatever cache size and the cpu thread to use that you specified. It will only run 2 tasks irrespective of your cache size. However there is a bug in the boinc manager (not sure what version that is) that could potentially load more tasks that you need and override the cache size. Just fyi. The bug has been fixed in the latest versions of the Boinc Client. Even before that, I have been running max_concurrent with a small cache size for several years without a problem - each project (including SiDock and CPDN) working according to their project weighting. (If anything it’s WCG that overfills the cache with respect to its project weighting). Hi Bryn Yeah i use BOINC 8.0.0 already, so you say that if I set <max_concurrent>1</max_concurrent> will only request 1 task from server ? I only will be able to try this in few days or so cause I need to crunch multiple SiDock tasks that i already got .. Thank you
5) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2247) Posted 27 days ago by rilian Post: Agree. That would be the easiest approach. Not sure if this will be the project admin top priority or working on the research project. Most of us here look for alternative solution such as running multiple boinc clients. BTW, this is commonly used during boinc competition. Thank you Yes I realize this technique could be helpful for bunkering WUs :) I left a message to project admin, will see what they reply...
6) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2245) Posted 27 days ago by rilian Post: ouch… then it would be great if admin set the setting or make tasks smaller..
7) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2243) Posted 27 days ago by rilian Post: Set up an appconfig.xml file in the SiDock project directory with a max_concurrent command :- https://boinc.berkeley.edu/trac/wiki/ClientAppConfig Thank you @Bryn, this looks like easiest solution, will try Thanks @pututu
8) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2240) Posted 27 days ago by rilian Post: Thank you for reply @pututu. Let me clarify Besides Sidock, I crunch multiple projects (wcg, rosetta etc) which may have tasks outage periods, that is why i keep setting to cache work for ~1 day Computer has 8 CPUs and about 40-60 various tasks in the queue, and usually with these projects, the task deadlines are quite short, for example 3 days with Rosetta. Sidock has about 6 days to deadline Other projects crunch a task in about 1-3 hours, while Sidock crunches in about 2 days Computer is 80% turned on. So, when Boinc client requests Sidock, computer usually gets 8 tasks and this immediately puts all tasks at risk cause instead of 1 day cache it now has ~3 days cache and this causes Boinc to juggle the tasks It would be more convenient to set a limit to avoid such issue
9) Message boards : Number crunching : Is it possible to turn on the setting "Max # of simultaneous tasks" ? (Message 2238) Posted 28 days ago by rilian Post: Hi, because currently Sidock only gives long tasks that take 1.5-3 days on average computer, and Sidock deadlines are very short, when computer receives multiple tasks this blocks computation of other projects Many other projects allow to set "Max # of simultaneous tasks" which allows to pick projects more easily for crunchers Could you please enable this setting ? Thank you!