Differences

This shows you the differences between two versions of the page.

--- cluster:134 [2014/08/17 13:14]
hmeij [High Throughput]
+++ cluster:134 [2014/08/19 15:33]
hmeij [High Throughput]
@@ Line 103: / Line 103: @@
 [[https://computing.llnl.gov/linux/slurm/high_throughput.html]]
-  * MaxJobCount=100000
+  * MaxJobCount=120000
   * SlurmctldPort=6820-6825
   * SchedulerParameters=max_job_bf=100,interval=30  (NOTE:  unset these, pages states default values are fine)
-^NrJobs^N^hh:mm^
+^NrJobs^N^hh:mm^N^hh:mm^
-|50,000|8|00:56|
+|50,000|8|00:56|  |  |
-|75,000|8|01:53|
+|75,000|8|01:53|16|01:57|
-|100,000|8|03:20|
+|100,000|8|03:20|  |  |
+The N=16 is 8 one core VMs and swallowtail itself (8 cores). So we're sxheduling bound. But 50,000 jobs per hour is grand! Certainly would exceed what we throw at it. And that's on old hardware.
+<code>
+WARNING: We will use a much slower algorithm with proctrack/pgid, use
+Proctracktype=proctrack/linuxproc or some other proctrack when using jobacct_gather/linux
+</code>
+After fixing that. (I also added a proplog/epilog script to my submit job script which will created /localscratch/$SLURM_JOB_ID, echo the date into file foo, then cat foo to standard out). These prolog/epilog actions needs to be done by slurmd but so far it errors for me.
+^NrJobs^N^hh:mm^N^hh:mm^
+|50,000|8|00:??|
- WARNING: We will use a much slower algorithm with proctrack/pgid, use Proctracktype=proctrack/linuxproc or some other proctrack when using jobacct_gather/linux
 Debug Level is 3. Maybe go to 1.

DokuWiki