- Timestamp:
- Nov 16, 2011, 3:00:39 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/oar/oar-dispatch
r10 r11 123 123 --help 124 124 125 File name content can have125 Input job file name content can have 126 126 127 127 - empty line … … 132 132 just after C<oarsub>. 133 133 134 Example where F<$HOME/test/subjob 1.oar> is an OAR script job (executable).134 Example where F<$HOME/test/subjob.txt> is a list of OAR script job (and can be executable but not need here). 135 135 136 136 oarsub -n test -l /core=1,walltime=00:05:00 $HOME/test/subjob1.oar … … 143 143 oarsub -n test -l /core=1,walltime=00:05:00 $HOME/test/subjob40.oar 144 144 145 These jobs could be launch by145 These jobs could be launch with 146 146 147 147 oarsub -t container -n test-container -l /core=6,walltime=00:35:00 "oar-dispatch -f ./subjob.list.txt" 148 148 149 Total C<walltime> is define by the formula:149 Total C<walltime> is defined by the formula: 150 150 151 151 total_walltime = subjob_walltime * total_subjob / core + global_delay 152 152 153 In practise, C<oar-dispatch> take few second and each subjob run less than it's walltime so153 In practise, C<oar-dispatch> take few second and each subjob run in less than it's walltime so 154 154 155 155 total_walltime < subjob_walltime * total_subjob / core
Note: See TracChangeset
for help on using the changeset viewer.