User Tools

Site Tools


memory_reservation

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
memory_reservation [2017/08/20 17:48]
meesters
memory_reservation [2018/06/27 10:12] (current)
henkela
Line 24: Line 24:
 The CPU time divided by the number of used CPUs should more or less equal elapsed run time. Otherwise, this is an indication for poor parallelisation. The CPU time divided by the number of used CPUs should more or less equal elapsed run time. Otherwise, this is an indication for poor parallelisation.
  
 +<WRAP center round info 80%>
 +On **Mogon 2** we use a JobSubmit-Plugin to manage memory reservation in case the user didn't speficy one. If the job is going to the broadwell nodes the default memory per node is 57.000MB. On the other hand, if the job is going to the skylake nodes the default memory per node will be set to 88.500MB.
 +For the bigmem-partition the process runs vice versa. If you specify memory per node > 1TB without specifying constrain broadwell or skylake you'll get skylake since that's the only nodes that support up to 1,5TB. For anything < 1TB you'll get broadwell if you don't specify anything different.
 +</​WRAP>​
memory_reservation.txt · Last modified: 2018/06/27 10:12 by henkela