Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I manually edited a submission script to change the memory requirements – why won LSF schedule the job?

0
Posted

I manually edited a submission script to change the memory requirements – why won LSF schedule the job?

0

In general we don’t recommend manually editing submission scripts generated previously by the queuename commands and submitting them to create new jobs, or writing submission scripts from first principles, as there are a number of subtleties which the automatic method takes care of, and which manual methods can easily miss. One such subtlety is the fact that the memory requirements of a job need to be stated in TWO places: # BSUB -M total_mem_in_KB # BSUB -R “rusage[mem=mem_per_cpu_in_MB:duration=15m:decay=1]” The difference between these two statements (apart from the syntax and the fact that one is given in terms of total job memory in KB, and the other in terms of per cpu memory in MB), is as follows. The first (-M) statement imposes an operating system limit on each process of the job which none may exceed without punitive action being taken (by the operating system); this is to protect the system from runaway jobs taking excessive amounts of memory. The second (-R) statement indic

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123