[Beowulf] When is compute-node load-average "high" in the HPC context? Setting correct thresholds on a warning script.
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Rahul Nabar rpnabar at gmail.comWed Sep 1 08:18:06 PDT 2010
- Previous message: [Beowulf] GPU
- Next message: [Beowulf] When is compute-node load-average "high" in the HPC context? Setting correct thresholds on a warning script.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Sep 1, 2010 at 3:47 AM, Reuti <reuti at staff.uni-marburg.de> wrote: > My impression was always (as there is a similar setting for the load_threshold in OGE), that it should limit the number of jobs on a big SMP machine when you oversubscribe by intention, as not all parallel jobs are really using all the CPU power over their lifetime (maybe such a machine was even operated w/o any NFS). Then allowing e.g. 72 slots for jobs on a 60 core maschine might get most out of it with a load near 100%. Our scheduler is currently set as to never allow over-subscription. Also, we don't allocate shared nodes. Users get resources in 8-core increments. -- Rahul
- Previous message: [Beowulf] GPU
- Next message: [Beowulf] When is compute-node load-average "high" in the HPC context? Setting correct thresholds on a warning script.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list