Differences
This shows you the differences between two versions of the page.
Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
cluster:134 [2014/08/19 15:50] hmeij [High Throughput] |
cluster:134 [2014/08/20 13:03] hmeij [High Throughput] |
</code> | </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 and finish with removing the scratch dir). These prolog/epilog actions needs to be done by slurmd but so far it errors for me. | After fixing that. Hmmm. |
| |
| ^NrJobs^N^hh:mm^ |
| | 1,000|8|00:02| |
| |10,000|8|00:22| |
| |15,000|8|00:31| |
| |20,000|8|00:41| |
| |
| |
| Debug Level is 3 above. Falling back to proctrack/pgid while setting debug to level 1. Also setting SchedulerType=sched/builtin (removing the backfill). This is throughput allright, just 8 KVM nodes handling the jobs. |
| |
| ^NrJobs^N^hh:mm:00^ |
| | 1,000|8|00:00:34| |
| |10,000|8|00:05:57| |
| |25,000|8|00:15:07| |
| |50,000|8|00:29:55| |
| |75,000|8|00:44:15| |
| |50,000|8|00:58:16| |
| |
| Now 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 and finish with removing the scratch dir. These prolog/epilog actions needs to be done by slurmd but so far it errors for me. Does slow things down a bit. Same conditions as above. |
| |
^NrJobs^N^hh:mm^N^hh:mm^ | |
|50,000|8|00:??| | |
| |
| |
Debug Level is 3. Maybe go to 1. | |
| |
\\ | \\ |
**[[cluster:0|Back]]** | **[[cluster:0|Back]]** |