HTCondorWiki: Running Matlab

 
 Matlab may try to create a graphical environment.  Condor does not support graphical environments; it doesn't make sense to open up a user interface for a job that won't have a user directly looking at it.  You may need some combination of -nosplash, -nodisplay, and possibly -nojvm to stop Matlab from creating a graphical environment. This should not be necessary for Matlab Compiler compiled jobs.
 
+Unless you have special arrangements to use multiple CPU cores, you will want -singleCompThread so that Matlab only uses a single core.
+
+|-nosplash         | Disable splash screen. (No GUI support in Condor)|
+|-nodisplay        | Disable GUI. (No GUI support in Condor)|
+|-nojvm            | Disable GUI? Eliminate unnecessary Java (faster?)|
+|-singleCompThread | Only use one CPU core (play nicely when sharing computer|
+
+
+
 {section: Parallelism}
 
 In the most common configuration, Condor does not directly support "parallel" jobs, jobs that might use a system like MPI or multiple threads to take advantage of multiple CPUs at once.  Condor can launch jobs that use multiple processes or threads, but by default Condor will offer them a single CPU core to run on.  (They may get lucky and be able to use more than one CPU core on a computer, but that should not be relied on.)
@@ -78,7 +87,8 @@
 end
 {endcode}
 
-*TODO*: Is the lastN necessary?
+*: *TODO*: Is the lastN necessary?
+*: *TODO*: maxNumCompThreads is deprecated. The preferred solution is to pass "-singleCompThread" on the command line. _check if -singleCompThread works for compiled jobs_, we don't think it does.
 
 {section: Additional Resources}