Q. How to correctly compute the solver scale up for parallel runs?
A. When computing solver scale up for parallel runs, the correct 'Clock Time' to use is the "CFD Solver wall clock seconds" printed right after the last iteration in the Output file. Example:
======================================================================
OUTER LOOP ITERATION = 784 ( 200) CPU SECONDS = 3.593E+03 (1.068E+03)

 Equation  Rate  RMS Res  Max Res  Linear Solution 
++++++
 UMom  0.97  1.5E05  3.3E04  6.9E03 OK
 VMom  0.98  3.1E06  9.4E05  1.6E02 OK
 WMom  1.05  4.1E06  3.6E05  6.2E03 OK
 PMass  0.82  2.4E06  3.3E05  8.5 2.9E02 OK
++++++
 HEnergy  0.90  4.0E05  8.7E04  5.6 6.1E03 OK
++++++
 KTurbKE  0.87  1.1E05  4.2E04  5.6 1.1E02 OK
 EDiss.K  0.71  1.5E05  4.5E04  7.1 4.1E03 OK
++++++
 Water Vapour at 100  0.94  3.4E05  7.2E04  5.6 1.7E02 OK
++++++
CFD Solver finished: Thu Jun 9 13:51:42 2005
CFD Solver wall clock seconds: 1.1380E+03
All other CPU times and Wall clocks times reported will include disk I/O overheads and partitioning overheads and hence will not give a true representation of the the solver scale up as you add partitions.
Q. How to correctly compute the solver scale up for parallel runs? A. When computing solver scale up for parallel runs, the correct 'Clock Time' to use is the "CFD Solver wall clock seconds" printed right after the last iteration in the Output file. Example: ====================================================================== OUTER LOOP ITERATION = 784 ( 200) CPU SECONDS = 3.593E+03 (1.068E+03)   Equation  Rate  RMS Res  Max Res  Linear Solution  ++++++  UMom  0.97  1.5E05  3.3E04  6.9E03 OK  VMom  0.98  3.1E06  9.4E05  1.6E02 OK  WMom  1.05  4.1E06  3.6E05  6.2E03 OK  PMass  0.82  2.4E06  3.3E05  8.5 2.9E02 OK ++++++  HEnergy  0.90  4.0E05  8.7E04  5.6 6.1E03 OK ++++++  KTurbKE  0.87  1.1E05  4.2E04  5.6 1.1E02 OK  EDiss.K  0.71  1.5E05  4.5E04  7.1 4.1E03 OK ++++++  Water Vapour at 100  0.94  3.4E05  7.2E04  5.6 1.7E02 OK ++++++ CFD Solver finished: Thu Jun 9 13:51:42 2005 CFD Solver wall clock seconds: 1.1380E+03 All other CPU times and Wall clocks times reported will include disk I/O overheads and partitioning overheads and hence will not give a true representation of the the solver scale up as you add partitions. 

