Faq Improve performance with PLS Toolbx and Solo: Difference between revisions
imported>Lyle (Created page with "===Issue:=== How can I improve performance with PLS_Toolbox and Matlab on the Mac platform? ===Possible Solutions:=== Some combinations of PLS_Toolbox and Matlab can experi...") |
imported>Scott m (Scott moved page Faq improve performance with PLS Toolbx and Matlab on Mac to Faq Improve performance with PLS Toolbx and Solo: Need general solution to performance faq) |
||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
===Issue:=== | ===Issue:=== | ||
How can I improve performance with PLS_Toolbox and | How can I improve performance with PLS_Toolbox and or Solo? | ||
===Possible Solutions:=== | ===Possible Solutions:=== | ||
There are several areas where performance and be improved. | |||
See the [[ToolboxPerformance|toolbox performance]] page for a general measure of expected performance. | |||
NOTE: We follow best practices for code performance in Matlab such as vectorization, preallocation, and file I/O. | |||
====Hardware==== | |||
* Use a 64bit operating system. | |||
* Use as much RAM as possible. | |||
* Use SSD (solid state drive) hard drive. | |||
* Follow The Mathworks guidelines for hardware: | |||
::* https://www.mathworks.com/support/requirements/choosing-a-computer.html | |||
====Software==== | |||
* Try a different version of Matlab. There were big changes to Matlab after 2014a that impacted graphics performance. If you have access to 2014a try using it. Otherwise try using the latest version of Matlab you can get you hands on. | |||
* Close unused programs. | |||
* Close unused PLS_Toolbox/Solo windows. | |||
* Perform preprocessing [[Faq_getting_out_of_memory_errors_when_using_preprocessing_in_GUI|separately]]. | |||
* Use memory saving steps found [[Faq_out_of_memory_error_when_analyzing_data|here]]. | |||
====Graphics==== | |||
Graphics will benefit from all | |||
* Be sure your drivers are up to date. | |||
* Try changing your renderer: | |||
:: https://www.mathworks.com/matlabcentral/answers/157894-resolving-low-level-graphics-issues-in-matlab | |||
* Down-sample the data. These tools can be used: | |||
:* coadd_img | |||
===Older Solution=== | |||
The solution below is a version specific to older versions of PLS_Toolbox on the Mac platform (roughly 2008-2014): | |||
Some combinations of PLS_Toolbox and Matlab can experience performance issues. These issues can be the result of a combination of factors involving both PLS_Toolbox and or Matlab. We recommend one or more of the following: | |||
</ | #Use the latest version of PLS_Toolbox. In some cases we've been able fix problems associated with Mac performance. | ||
</ | #Try changing the Java Heap Size from the Matlab → Preferences → Java Heap Memory menu item. Select the largest amount available (e.g., 256MB). | ||
#For Matlab versions 2011a and newer, disable Screen Menus via the java.opts file. Save all of your work then from the Matlab Command window enter: | |||
#: <code>>> edit(fullfile(matlabroot,'bin','maci64','java.opts'))</code> | |||
#:then add the following line: | |||
#:<code> -Dapple.laf.useScreenMenuBar=false</code> | |||
#:save the file and restart Matlab. | |||
#Try using a different version of Matlab. Depending on the version of hardware and PLS_Toolbox, some [older] versions of Matlab may work better than others. Newer versions (2011a-2012a) seem to require disabling of screen menus and increased Heap size (steps 2 and 3). In general we recommend the newest version of Matlab available. | |||
#Hide the model cache. Sometimes the java tree component seems to slow things down. Hiding the cache when not in use may help. From the Analysis Tools menu select View Cache → Hide Cache Viewer. | |||
#Set javaopts to use Quartz rendering (via the java opts as above). | |||
#:<code>-Dapple.awt.graphics.UseQuartz=true</code> | |||
#Restart Matlab often (daily). This is probably the most effective way to keep performance from dropping. | |||
The Mathworks has stated to us in response to service requests (FEB 2012): | |||
<nowiki>"Currently, MATLAB graphics performance can be better under Windows than Mac. The Win API supports "immediate mode" drawing, and the "deferred mode" on OS X limits the raw performance vs. Windows. Also Intel has not made available for OS X a version of their compiler which supports PGO."</nowiki> | |||
'''Still having problems? Please contact our helpdesk at [mailto:helpdesk@eigenvector.com helpdesk@eigenvector.com]''' | |||
[[Category:FAQ]] | [[Category:FAQ]] |
Latest revision as of 13:33, 8 July 2019
Issue:
How can I improve performance with PLS_Toolbox and or Solo?
Possible Solutions:
There are several areas where performance and be improved.
See the toolbox performance page for a general measure of expected performance.
NOTE: We follow best practices for code performance in Matlab such as vectorization, preallocation, and file I/O.
Hardware
- Use a 64bit operating system.
- Use as much RAM as possible.
- Use SSD (solid state drive) hard drive.
- Follow The Mathworks guidelines for hardware:
Software
- Try a different version of Matlab. There were big changes to Matlab after 2014a that impacted graphics performance. If you have access to 2014a try using it. Otherwise try using the latest version of Matlab you can get you hands on.
- Close unused programs.
- Close unused PLS_Toolbox/Solo windows.
- Perform preprocessing separately.
- Use memory saving steps found here.
Graphics
Graphics will benefit from all
- Be sure your drivers are up to date.
- Try changing your renderer:
- Down-sample the data. These tools can be used:
- coadd_img
Older Solution
The solution below is a version specific to older versions of PLS_Toolbox on the Mac platform (roughly 2008-2014):
Some combinations of PLS_Toolbox and Matlab can experience performance issues. These issues can be the result of a combination of factors involving both PLS_Toolbox and or Matlab. We recommend one or more of the following:
- Use the latest version of PLS_Toolbox. In some cases we've been able fix problems associated with Mac performance.
- Try changing the Java Heap Size from the Matlab → Preferences → Java Heap Memory menu item. Select the largest amount available (e.g., 256MB).
- For Matlab versions 2011a and newer, disable Screen Menus via the java.opts file. Save all of your work then from the Matlab Command window enter:
>> edit(fullfile(matlabroot,'bin','maci64','java.opts'))
- then add the following line:
-Dapple.laf.useScreenMenuBar=false
- save the file and restart Matlab.
- Try using a different version of Matlab. Depending on the version of hardware and PLS_Toolbox, some [older] versions of Matlab may work better than others. Newer versions (2011a-2012a) seem to require disabling of screen menus and increased Heap size (steps 2 and 3). In general we recommend the newest version of Matlab available.
- Hide the model cache. Sometimes the java tree component seems to slow things down. Hiding the cache when not in use may help. From the Analysis Tools menu select View Cache → Hide Cache Viewer.
- Set javaopts to use Quartz rendering (via the java opts as above).
-Dapple.awt.graphics.UseQuartz=true
- Restart Matlab often (daily). This is probably the most effective way to keep performance from dropping.
The Mathworks has stated to us in response to service requests (FEB 2012):
"Currently, MATLAB graphics performance can be better under Windows than Mac. The Win API supports "immediate mode" drawing, and the "deferred mode" on OS X limits the raw performance vs. Windows. Also Intel has not made available for OS X a version of their compiler which supports PGO."
Still having problems? Please contact our helpdesk at helpdesk@eigenvector.com