User Tools

Site Tools


io_reservation

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
io_reservation [2015/05/19 13:18]
meesters [I/O bandwidth reservation]
io_reservation [2016/04/28 11:28]
schlarbm
Line 21: Line 21:
 ==== PLEASE NOTE ==== ==== PLEASE NOTE ====
  
-1. If the rusage parameter is omitted by a user, LSF will automatically add the parameter -R "​rusage[atlasio=10]"​.+1. If the rusage parameter is omitted by a user, LSF will automatically add the parameter ​''​-R "​rusage[atlasio=10]"​''​.
  
-2. For jobs that will not do a reasonable amount (sum of all files < 100MByte) of I/O, the user should specify the parameter with 0 MB/s -R "​rusage[atlasio=0]"​ otherwise - like mentioned before - 10MB/s will be assumed.+2. For jobs that will not do a reasonable amount (sum of all files < 100MByte) of I/O, the user should specify the parameter with 0 MB/s ''​-R "​rusage[atlasio=0]"​'' ​otherwise - like mentioned before - 10MB/s will be assumed.
  
 3. For multiprocessor jobs the value posted with //atlasio// is taken into account per core. e.g. a 2 core job will reserve 2 times the //atlasio// value: 3. For multiprocessor jobs the value posted with //atlasio// is taken into account per core. e.g. a 2 core job will reserve 2 times the //atlasio// value:
io_reservation.txt · Last modified: 2017/06/30 08:35 by meesters