Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
doku:gromacs [2023/11/23 11:51] msiegeldoku:gromacs [2023/11/23 12:18] – [Many nodes with many GPUs] msiegel
Line 253: Line 253:
 In most cases one node is **better** than more nodes. In most cases one node is **better** than more nodes.
  
-In some cases, for example a large molecule like Test 7, you might want to run GROMACS on multiple nodes in parallel using MPI, with multiple GPUs (one each node). We strongly encourage you to test if you actually benefit from running with GPUs on many nodes. GROMACS can perform worse on many nodes in parallel than on a single one, even considerably!+In some cases, for example a large molecule like Test 7, you might want to run GROMACS on multiple nodes in parallel using MPI, with multiple ''A100'' GPUs (one each node). We strongly encourage you to test if you actually benefit from running with GPUs on many nodes. GROMACS can perform worse on many nodes in parallel than on a single one, even considerably!
  
 Run GROMACS on multiple nodes with: Run GROMACS on multiple nodes with:
Line 274: Line 274:
     }, {     }, {
         name: 'Test 3',         name: 'Test 3',
-        data: [ 00000]+        data: [ 94.06999.78897.9100.50995.66683.485 ]
     }, {     }, {
         name: 'Test 4',         name: 'Test 4',
-        data: [ 00000, 0 ]+        data: [ 115.179117.999115.028114.967103.8, 0 ]
     }, {     }, {
         name: 'Test 5',         name: 'Test 5',
Line 323: Line 323:
 } }
 </achart> </achart>
 +
 +Note: the computation timed out for 4 with 32 nodes, before gromacs was able to estimate a performance. We can safely assume this example case is going to be less performant on 32 than on fewer nodes too.
  
  
  • doku/gromacs.txt
  • Last modified: 2023/11/23 12:27
  • by msiegel