Lyang at 13:35, 4 December 2020

2020-12-04T13:35:33Z

Lyang: Created page with "== What to do when you get "Out of Memory" errors == Users may see "out of memory" errors when they run their jobs. In most cases, this indicates that users try to use more me..."

2020-12-02T14:15:12Z

Created page with "== What to do when you get "Out of Memory" errors == Users may see "out of memory" errors when they run their jobs. In most cases, this indicates that users try to use more me..."

New page

== What to do when you get "Out of Memory" errors ==
Users may see "out of memory" errors when they run their jobs. In most cases, this indicates that users try to use more memory than DeepSense systems can provide. However, users may try to run too many scripts on a single machine that use up all the available memory. This can be easily avoided by submitting new LSF jobs.<br>
Here's a scenario why this error occurs. For example, a user submits an interactive LSF job and is assigned a session on a compute node. A user running interactive LSF jobs would have more control of the compute node than batch jobs. Users are able to manually run a lot of scripts on the compute node. If a user runs too many scripts in the same session, the memory could be used up by his/her scripts. In such a situation, the user should stop running too many scripts and submit new jobs to get new sessions. The new sessions would be open for the user with newly assigned resources. This scenario mostly happens for interactive LSF jobs.<br>
However, if you experience memory issues running batch jobs, please contact DeepSense support. We will investigate what is happening and provide you help.

← Older revision		Revision as of 13:35, 4 December 2020
Line 3:		Line 3:
	Here's a scenario why this error occurs. For example, a user submits an interactive LSF job and is assigned a session on a compute node. A user running interactive LSF jobs would have more control of the compute node than batch jobs. Users are able to manually run a lot of scripts on the compute node. If a user runs too many scripts in the same session, the memory could be used up by his/her scripts. In such a situation, the user should stop running too many scripts and submit new jobs to get new sessions. The new sessions would be open for the user with newly assigned resources. This scenario mostly happens for interactive LSF jobs.<br>		Here's a scenario why this error occurs. For example, a user submits an interactive LSF job and is assigned a session on a compute node. A user running interactive LSF jobs would have more control of the compute node than batch jobs. Users are able to manually run a lot of scripts on the compute node. If a user runs too many scripts in the same session, the memory could be used up by his/her scripts. In such a situation, the user should stop running too many scripts and submit new jobs to get new sessions. The new sessions would be open for the user with newly assigned resources. This scenario mostly happens for interactive LSF jobs.<br>
	However, if you experience memory issues running batch jobs, please contact DeepSense support. We will investigate what is happening and provide you help.		However, if you experience memory issues running batch jobs, please contact DeepSense support. We will investigate what is happening and provide you help.
		+
		+	== Where is my job output file? ==
		+	Output may not be written to the specified file immediately when using the <code>-o <filename></code> or <code>-oo <filename></code> options. There are two workarounds for this problem:
		+
		+	# You can use the bpeek <jobid> command to view the output of a currently running job.
		+	# You can send your output to a file with the typical unix output specifications such as <code>> <filename></code> with your executed programs or by specifying output files in programs that support such options.

LSF Jobs - Revision history

Lyang at 13:35, 4 December 2020

Lyang: Created page with "== What to do when you get "Out of Memory" errors == Users may see "out of memory" errors when they run their jobs. In most cases, this indicates that users try to use more me..."