Difference between revisions of "Comsol/Batch"

From ScientificComputing
Jump to: navigation, search
Line 1: Line 1:
 
Your COMSOL jobs have to be submitte to the batch system. For a single processor calculation a typical command is
 
Your COMSOL jobs have to be submitte to the batch system. For a single processor calculation a typical command is
  
   bsub [LSF-parameters] comsol batch -inputfile infile.mph -outputfile outfile.mph  
+
   bsub [LSF options] comsol batch -inputfile infile.mph -outputfile outfile.mph  
  
LSF-parameters are documented on the wiki page about [[Using_the_batch_system|using the batch system]].
+
Here you need to replace ''[LSF options]'' with LSF parameters for the resource requirements of the job. Please find a documentation about the parameters of bsub  on the wiki page about the [[Using_the_batch_system|batch system]].
  
 
===Parallel jobs using shared memory===
 
===Parallel jobs using shared memory===
 
For parallel jobs using shared memory, you can specify the number of cores to be used with the '''-np''' option of COMSOL:
 
For parallel jobs using shared memory, you can specify the number of cores to be used with the '''-np''' option of COMSOL:
  
   bsub '''-n 4''' [LSF-parameters] comsol batch '''-np 4''' -inputfile infile.mph -outputfile outfile.mph  
+
   bsub '''-n 4''' [LSF options] comsol batch '''-np 4''' -inputfile infile.mph -outputfile outfile.mph  
  
Please make sure that the '''-n''' option ob '''bsub''' and the '''-np''' option of COSMOL always have the same value. Please be careful to not use the '''-clustersimple''' option for shared memory jobs as this would make COMSOL start MPI processes instead of using threads.
+
LSF options are documented on the wiki page about [[Using_the_batch_system|using the batch system]]. Please make sure that the '''-n''' option ob '''bsub''' and the '''-np''' option of COSMOL always have the same value. Please be careful to not use the '''-clustersimple''' option for shared memory jobs as this would make COMSOL start MPI processes instead of using threads.
  
 
If you plan to run parallel COMSOL jobs, then we strongly recommend to first do a small scaling study to find out the sweet spot for the parallel efficiency of your model. Since COMSOL can be strongly memory bound, the sweet spot might be to use 4 cores (see scaling study below).
 
If you plan to run parallel COMSOL jobs, then we strongly recommend to first do a small scaling study to find out the sweet spot for the parallel efficiency of your model. Since COMSOL can be strongly memory bound, the sweet spot might be to use 4 cores (see scaling study below).
Line 20: Line 20:
 
   bsub '''-n 4''' [LSF-parameters] comsol batch '''-clustersimple''' -inputfile infile.mph -outputfile outfile.mph
 
   bsub '''-n 4''' [LSF-parameters] comsol batch '''-clustersimple''' -inputfile infile.mph -outputfile outfile.mph
  
Please be careful to not mix the '''-clustersimple''' option with the '''-np''' option as this will lead to the problems described troubleshooting section of this page.
+
LSF options are documented on the wiki page about [[Using_the_batch_system|using the batch system]]. Please be careful to not mix the '''-clustersimple''' option with the '''-np''' option as this will lead to the problems described troubleshooting section of this page.
  
 
If you plan to run parallel COMSOL jobs, then we strongly recommend to first do a small scaling study to find out the sweet spot for the parallel efficiency of your model. Since COMSOL can be strongly memory bound, the sweet spot might be to use 4 cores (see scaling study below).
 
If you plan to run parallel COMSOL jobs, then we strongly recommend to first do a small scaling study to find out the sweet spot for the parallel efficiency of your model. Since COMSOL can be strongly memory bound, the sweet spot might be to use 4 cores (see scaling study below).

Revision as of 05:47, 26 August 2016

Your COMSOL jobs have to be submitte to the batch system. For a single processor calculation a typical command is

 bsub [LSF options] comsol batch -inputfile infile.mph -outputfile outfile.mph 

Here you need to replace [LSF options] with LSF parameters for the resource requirements of the job. Please find a documentation about the parameters of bsub on the wiki page about the batch system.

Parallel jobs using shared memory

For parallel jobs using shared memory, you can specify the number of cores to be used with the -np option of COMSOL:

 bsub -n 4 [LSF options] comsol batch -np 4 -inputfile infile.mph -outputfile outfile.mph 

LSF options are documented on the wiki page about using the batch system. Please make sure that the -n option ob bsub and the -np option of COSMOL always have the same value. Please be careful to not use the -clustersimple option for shared memory jobs as this would make COMSOL start MPI processes instead of using threads.

If you plan to run parallel COMSOL jobs, then we strongly recommend to first do a small scaling study to find out the sweet spot for the parallel efficiency of your model. Since COMSOL can be strongly memory bound, the sweet spot might be to use 4 cores (see scaling study below).

Parallel jobs using distributed memory

If you would like to run COMSOL in distributed memory mode, then you need to add the -clustersimple option to your COMSOL command:

 bsub -n 4 [LSF-parameters] comsol batch -clustersimple -inputfile infile.mph -outputfile outfile.mph

LSF options are documented on the wiki page about using the batch system. Please be careful to not mix the -clustersimple option with the -np option as this will lead to the problems described troubleshooting section of this page.

If you plan to run parallel COMSOL jobs, then we strongly recommend to first do a small scaling study to find out the sweet spot for the parallel efficiency of your model. Since COMSOL can be strongly memory bound, the sweet spot might be to use 4 cores (see scaling study below).