Superjobs guillimin : Différence entre versions
m (Created page with "= Superjobs = A "superjob" is a job which runs on one of the normal queues and executes other jobs, which got submitted to a faked queue, one after the other. '''NEVER KILL&n...") |
m |
||
| Ligne 1: | Ligne 1: | ||
= Superjobs = | = Superjobs = | ||
| − | A "superjob" is a job which runs on one of the normal queues and executes other jobs, which got submitted to a faked queue, one after the other. | + | A "superjob" is a job which runs on one of the normal queues and executes other jobs, which got submitted to a faked queue, one after the other.<br>It will run until the required wallclock time is finished or until it does not find any job to execute for a certain time. |
| + | |||
| + | ''' NEVER KILL A SUPERJOB !!!''' See below for more information. | ||
| + | |||
| + | A superjob is a very useful tool to execute post processing jobs. It will make the submission of post processing jobs by the model independent of guillimin's "moods". No jobs will get lost or have to re resubmitted by hand. | ||
| + | |||
| − | |||
== How to start a "superjob" == | == How to start a "superjob" == | ||
| Ligne 13: | Ligne 17: | ||
Arguments_for_ord_soumet may include -q, -jn, and any other relevant argument<br> | Arguments_for_ord_soumet may include -q, -jn, and any other relevant argument<br> | ||
| − | Submission example: | + | '''Submission example''': |
u.run_work_stream -t ''2592000'' -cpus ''1'' -name ''superjob_1a'' -maxidle ''36000'' -queues ''sj1'' -- -q ''sw'' -jn ''superjob_1a'' | u.run_work_stream -t ''2592000'' -cpus ''1'' -name ''superjob_1a'' -maxidle ''36000'' -queues ''sj1'' -- -q ''sw'' -jn ''superjob_1a'' | ||
| − | In this case a superjob with the name '''superjob_1''' will get submitted. <br>'-name' is the interlan name of the superjob, '-jn' the name of the listing.<br>For simplicity I suggest to keep the two names the same.<br>Make sure to '''NEVER HAVE TWO SUPERJOBS WITH THE SAME NAME''' running. But once a superjob has finished you can submit a new one with the same name. | + | In this case a superjob with the name '''superjob_1''' will get submitted. <br>''''-name'''' is the interlan name of the superjob, ''''-jn'''' the name of the listing.<br>For simplicity I suggest to keep the two names the same.<br>Make sure to '''NEVER HAVE TWO SUPERJOBS WITH THE SAME NAME''' running. But once a superjob has finished you can submit a new one with the same name. |
| + | |||
| + | The superjob will get submitted for ''''-t''' ''2592000''' seconds (30 days) on ''''-cpus'''''1''' cpu to the queue ''''-q''' ''sw'''. | ||
| + | |||
| + | If it does not find a job to execute for ''''-maxidle''' ''36000''' seconds it will terminate itself.<br> | ||
| − | The superjob will | + | The superjob will execute jobs which got submitted to the faked queue ''''-queues''' ''sj1'''.<br> |
<br> | <br> | ||
Version depuis le 9 de novembre 2012 à 20:31
Superjobs
A "superjob" is a job which runs on one of the normal queues and executes other jobs, which got submitted to a faked queue, one after the other.
It will run until the required wallclock time is finished or until it does not find any job to execute for a certain time.
NEVER KILL A SUPERJOB !!! See below for more information.
A superjob is a very useful tool to execute post processing jobs. It will make the submission of post processing jobs by the model independent of guillimin's "moods". No jobs will get lost or have to re resubmitted by hand.
How to start a "superjob"
The command to submit a superjob is "u.run_work_stream":
u.run_work_stream [-instances n] -t mseconds -cpus number_of_cpus -name stream_name -maxidle nseconds -queues q1 q2 ... qn [--] "arguments_for_ord_soumet"
Arguments_for_ord_soumet may include -q, -jn, and any other relevant argument
Submission example:
u.run_work_stream -t 2592000 -cpus 1 -name superjob_1a -maxidle 36000 -queues sj1 -- -q sw -jn superjob_1a
In this case a superjob with the name superjob_1 will get submitted.
'-name' is the interlan name of the superjob, '-jn' the name of the listing.
For simplicity I suggest to keep the two names the same.
Make sure to NEVER HAVE TWO SUPERJOBS WITH THE SAME NAME running. But once a superjob has finished you can submit a new one with the same name.
The superjob will get submitted for ''-t 2592000 seconds (30 days) on '-cpus1 cpu to the queue '-q sw.
If it does not find a job to execute for ''-maxidle 36000 seconds it will terminate itself.
The superjob will execute jobs which got submitted to the faked queue ''-queues sj1.
