![]() ![]() Qdel blah* will delete all (your) jobs with the name blah* Qdel 4711 qdel -u $(/bin/whoami) qdel '*' Unlike in LSF there is no possibility to wait for a defined number or all DONE or EXIT jobs, all jobs have just to be finished in some way. Using qstat you will see that your second jobs is in the state hqw (hold queue waiting) until the first job is done. =Your job 336394 ("script.sh") has been submitted= With dependency jobs you can submit both jobs directly one after the other instead of waiting for the first job to be done. you submit a simulation in the first job and an analysis job to analyse the simulated data in the second job. Done jobs are not shown hereĪ dependency jobs is a job which waits for an other job to be finished.Į.g. So it's much easierer to have a look on the running jobs and compare their resource usage. Qsub -t 1-100 -b y /bin/sleep 1000 submits one job with 100 tasks We are strongly asking the users to use job arrays for large productions, as this means less work for the SGE scheduler and it is easierer to monitor for you and for us. Will send oyu a mail at the start and another mail at the end of your job. N do not send a mail, this is the default behaviour. There X is one or more of the following :ī send email at the beginning of the jobĪ send email when the job is rescheduled or aborted (killed) If you want to get mails from SGE you can use the So one should be consservativ with the resource requs to get a fast scheduling but not to conservative to prevent a fast killing Qsub -l h_vmem=3G,h_rt=2h will place your jobs in the short queue, if this queue is full your jobs will go to the default queue and so on.Īs this numbers are not only requirements to SGE but also limits, SGE will kill jobs which are overtaking these limits. If these queues are filled up SGE will put your jobs in queues with higher resource requirements : In these cases you have to take care by yourself to retrieve these files, unlike in LSF you have to specify if you want to get the output via mail.ĭefining resource requirements will help SGE to put your jobs in the queues which will fit to your jobs the best. If you don't define a path for the error and output files they will be written to the current working directorie, which is usually /tmp. If you want to execute a binary (or a file which is already on the target location) use the -b(inary) y(es) option. ![]() SGE will only copy the script which was defined at the qsub line, nothing else! Unlike in the LSF cluster we have NO standard batch queue in the SGE cluster, SGE makes a job matching every time a slots is freed in the cluster. ATTENTION : In SGE the help for a single command is shown by ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |