My job enters the queue successfully, but it waits a long time before it gets to run. How can I make my jobs spend less time waiting for cluster time?
The job scheduling software on the cluster makes decisions about how best to allocate the cluster nodes to individual jobs and users. There are ways to make your job more likely to get nodes faster. • Don’t ask for more time than you need. Using commands within your job submission file, it is possible to trace the real start time and end time of your job, and compare them to the original amount of time you asked for from the job scheduler. If your job asks for much more time than needed, the job scheduler will think it cannot provide computers when in reality the job could have fit into a timeslot successfully. This ties up cluster resources needlessly, and means your job could have been done already. Calling the date command from within job submission script, once just before calling the actual computation part of the job submission script, and again at the end of the script will place two timestamps into the job output file. Use this data as a sanity check against how much time to as
Related Questions
- What happens if one scheduled job runs over the time of the next scheduled job? Will the second job fail or just wait until the first is completed or will they run simultaneously?
- What are examples of yearly jobs, and how much time should I expect to spend on my job?
- How many jobs can be scheduled to run at any point in time?
