For older Matlab (Possibly pre 2011?), to ensure that Matlab only uses one core, put this in your Matlab script:
 
 {code}
-lastN = maxNumCompThreads(1);
+lastN = maxNumCompThreads(1);   (Pre r2009bsp1)
 {endcode}
 
 If you're using the Matlab Compiler, but want to use multiple threads when doing development, you could use something like this to limit Matlab to one thread only for compiled versions:
@@ -90,10 +90,14 @@
 end
 {endcode}
 
+If you do the above with R2009sp1 and newer and also use the -R -singleCompThread it will error out.
+
 *: *TODO*: Is the lastN necessary? Seems unlikely, unless Matlab gets cranky when return values are ignored.
 
 The above does not work on newer versions of Matlab, as maxNumCompThreads is deprecated.  Instead, pass the -singleCompThread option.  If you are using mcc (the Matlab compiler), add "-R -singleCompThread" to your compiler options.
 
+The best you can do is prevent the compiled job from using one thread per core. It will still have 5 threads with all the time on one of them. Java aps will use a few more threads. But you will have less then one thread per core which is what it will do on its own.
+
 {section: Example}
 
 This example assumes that Matlab is available in /opt/Matlab/bin.