Message boards : Server programs : How to limit number of jobs per host?
Message board moderation
Author | Message |
---|---|
Send message Joined: 5 May 10 Posts: 5 |
Hi, I'm running a boinc poject and my scientific application is pretty much resource demanding. So if a volunteer runs 2 or more jobs on one machine it slows down the machines very much. However, there is for now no easy way to fix that, so I thought there might be an option to limit the number of work units per host, in order to prevent crashing of users machines. Thanks. Waldy |
Send message Joined: 5 Oct 06 Posts: 5124 |
|
Send message Joined: 5 May 10 Posts: 5 |
Thanks, but I would like to limit it to just one application, because we have two different types of applications running. But I guess this option is just general for the entire project. Best, Waldy |
Send message Joined: 5 Oct 06 Posts: 5124 |
You didn't actually mention the two science applications in the OP! :-( So many of these legacy options in BOINC still have an implicit assumption that one project == one science application (give or take a platform or three). We're slowly leaning on David and the dev team to separate the controls out per <app_version>: this looks like another one that needs the treatment. |
Send message Joined: 5 May 10 Posts: 5 |
you'r riht I missed to mention that there is another application running in the project. However, this would be very nice to have. A general and app specific feature. Waldy |
Send message Joined: 29 Aug 05 Posts: 15552 |
David Anderson wrote: The latest BOINC server code provides for per-application limits on in-progress jobs, in-progress GPU jobs, and jobs returned per RPC. He posted that here. |
Send message Joined: 5 Oct 06 Posts: 5124 |
Just found much the same thing. David accepted the concept of moving 'max_wus_in_progress' from a project scope to an application scope (not app_version, as I originally had it) on 19 March (boinc_dev mailing list, thread "Preemption of very short tasks" (sic!)). But the implementation seems to be bound up with the "new credit" concept, which went to live test at SETI Beta on or about (appropriately) 1 April, but seems to have stalled since. I do hope the useful scoping issues aren't going to get dragged down by credit wars.... |
Copyright © 2024 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.