Difference between revisions of "Matlab configuration advice"
(→Java heap size) |
(→MDCS on Amazon EC2) |
||
| Line 23: | Line 23: | ||
# Create a JobManager in AdminCenter, start the workers (one at a time per node). | # Create a JobManager in AdminCenter, start the workers (one at a time per node). | ||
# From a client instance, connect to the JobManager. | # From a client instance, connect to the JobManager. | ||
| + | |||
| + | |||
| + | ''Revision 3284, authors: [[Ilya Kuprov]]'' | ||
Revision as of 09:32, 12 August 2016
Large-scale deployments
Protein simulations with up to 100 amino acids would fit into 64 GB of RAM, unless the relaxation superoperator is computed, in which case the requirement is 256 GB + 10 GB per node per 100 amino acids. The asymptotic run time scaling is linear on shared-memory systems.
Parallelization
If you plan to run lengthy parallel calculations, disable the parallel pool timeout (Matlab Ribbon / Parallel / Parallel Preferences) by unticking the "shut down and delete" box in the settings.
Java heap size
Matrix exponential caching and Clebsch-Gordan coefficients with L ranks in excess of 2,000 require a bigger Java heap size than Matlab's default. The size of the Java heap can be increased in Preferences.
MDCS on Amazon EC2
To set up a Matlab Distributed Computing Server cluster on Amazon EC2 cloud, follow these instructions:
- Start a single Windows instance without the Amazon firewall.
- Change the Administrator password to the one you prefer.
- Install Matlab 2013a or later with Distributed Computing Server option.
- Run addMatlabToWindowsFirewall.bat file as Administrator.
- Switch off Windows firewall.
- Run 'mdce install', then 'mdce start' as Administrator.
- Stop the mdce service and set it to "Manual" in the service settings.
- Set up Spinach and set the paths in Matlab.
- Shut down the instance and make an AMI.
- Spawn several instances from the AMI, pick a head node and log into it.
- Run admincenter.bat, feed it the node addresses and start the mdce services.
- Create a JobManager in AdminCenter, start the workers (one at a time per node).
- From a client instance, connect to the JobManager.
Revision 3284, authors: Ilya Kuprov