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/14 18:33] hmeij [25K+] |
cluster:134 [2014/08/20 16:53] hmeij [High Throughput] |
||
---|---|---|---|
Line 17: | Line 17: | ||
* logs to files not mysql for now | * logs to files not mysql for now | ||
* change some settings in slurm.conf, particularly | * change some settings in slurm.conf, particularly | ||
- | * FirstJObId, MaxJobId | + | * FirstJObId(1), MaxJobId(999999) |
- | * MaxJobCount=100000 | + | * MaxJobCount=120000 |
* MaxTaskPerNode=65533 | * MaxTaskPerNode=65533 | ||
- | * SRunEpilog/ | ||
* | * | ||
Then I created a simple file to test Slurm | Then I created a simple file to test Slurm | ||
Line 34: | Line 33: | ||
echo " | echo " | ||
- | echo DONE | + | date |
</ | </ | ||
Line 56: | Line 55: | ||
# time to process queues of different sizes (I stage them with the --begin parameter) | # time to process queues of different sizes (I stage them with the --begin parameter) | ||
# jobs do have to open the output files though, just some crude testing of slurm | # jobs do have to open the output files though, just some crude testing of slurm | ||
- | # scheduling | + | # scheduling |
^NrJobs^1, | ^NrJobs^1, | ||
Line 67: | Line 66: | ||
Slurm is installed on a PE2950 with dual quad cores and 16 GB of memory. It is part of my high priority queue and allocated to Openlava (v2.2). | Slurm is installed on a PE2950 with dual quad cores and 16 GB of memory. It is part of my high priority queue and allocated to Openlava (v2.2). | ||
- | My slurm compute nodes (v1-v8) are created in a virtual KVM environment on another PE2950 (2.6 Ghz, 16 GB ram) dual quad core with hyperthreading and virtualization turned on in the BIOS. Comments on how to build that KVM environment are here [[cluster: | + | My slurm compute nodes (v1-v8) are created in a virtual KVM environment on another PE2950 (2.6 Ghz, 16 GB ram) dual quad core with hyperthreading and virtualization turned on in the BIOS. Comments on how to build that KVM environment are here [[cluster: |
From slurm.conf | From slurm.conf | ||
Line 84: | Line 83: | ||
- | ==== 25K+ ==== | + | ==== IO error ==== |
At around 32K jobs I ran into IO problems. | At around 32K jobs I ran into IO problems. | ||
Line 93: | Line 92: | ||
</ | </ | ||
+ | |||
+ | Oh, this is OS error from ext3 file system, max files and dirs exceeded. | ||
+ | |||
+ | Switching " | ||
+ | |||
+ | |||
+ | ==== High Throughput ==== | ||
[[https:// | [[https:// | ||
- | * MaxJobCount=100000 | + | * MaxJobCount=120000 |
* SlurmctldPort=6820-6825 | * SlurmctldPort=6820-6825 | ||
- | * SchedulerParameters=max_job_bf=100, | + | * SchedulerParameters=max_job_bf=100, |
+ | |||
+ | ^NrJobs^N^hh: | ||
+ | |50, | ||
+ | |75, | ||
+ | |100, | ||
+ | |||
+ | The N=16 is 8 one core VMs and swallowtail itself (8 cores). So we're scheduling bound. But 50,000 jobs per hour is grand! Certainly would exceed what we throw at it. And that's on old hardware. | ||
+ | |||
+ | |||
+ | < | ||
+ | WARNING: We will use a much slower algorithm with proctrack/ | ||
+ | Proctracktype=proctrack/ | ||
+ | </ | ||
+ | |||
+ | After fixing that. Hmmm. | ||
+ | |||
+ | ^NrJobs^N^hh: | ||
+ | | 1, | ||
+ | |10, | ||
+ | |15, | ||
+ | |20, | ||
+ | |||
+ | |||
+ | Debug Level is 3 above. Falling back to proctrack/ | ||
+ | |||
+ | ^NrJobs^N^hh: | ||
+ | | 1, | ||
+ | |10, | ||
+ | |25, | ||
+ | |50, | ||
+ | |75, | ||
+ | |100, | ||
+ | |||
+ | Next I will add a proplog/ | ||
+ | / | ||
+ | |||
+ | < | ||
+ | # | ||
+ | / | ||
+ | |||
+ | #SBATCH --job-name=" | ||
+ | #SBATCH --output=" | ||
+ | #SBATCH --begin=10: | ||
+ | |||
+ | # unique job scratch dir | ||
+ | export MYLOCALSCRATCH=/ | ||
+ | cd $MYLOCALSCRATCH | ||
+ | pwd | ||
+ | |||
+ | echo " | ||
+ | date >> foo | ||
+ | cat foo | ||
+ | |||
+ | / | ||
+ | </ | ||
+ | |||
+ | |||
+ | ^NrJobs^N^hh: | ||
+ | | 1, | ||
+ | | 5, | ||
+ | |10, | ||
+ | |25, | ||