<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I just ran a test of Aspect on Lonestar using 48 processors with the box.prm sample (using more mesh refinement) and I got the following timings:<div><br></div><div><font class="Apple-style-span" face="Monaco">+---------------------------------------------+------------+------------+<br>| Total wallclock time elapsed since start | 429s | |<br>| | | |<br>| Section | no. calls | wall time | % of total |<br>+---------------------------------+-----------+------------+------------+<br>| Assemble Stokes system | 131 | 1.25s | 0.29% |<br>| Assemble temperature system | 131 | 3.06s | 0.71% |<br>| Build Stokes preconditioner | 30 | 1.71s | 0.4% |<br>| Build temperature preconditioner| 131 | 0.181s | 0.042% |<br>| Solve Stokes system | 131 | 4.6s | 1.1% |<br>| Solve temperature system | 131 | 1.68s | 0.39% |<br>| Postprocessing | 129 | 17.3s | 4% |<br>| Refine mesh structure, part 1 | 27 | 0.913s | 0.21% |<br>| Refine mesh structure, part 2 | 27 | 0.16s | 0.037% |<br>| Setup dof systems | 28 | 1.22s | 0.28% |<br>+---------------------------------+-----------+------------+------------+<br></font><br></div><div>In case the formatting is messed up, basically it seems the total wall time (429s) is about 13x greater than the sum of the sections. In other words, 397 seconds of run time are unaccounted for out of 429 total seconds. Are there any sections that could potentially account for this that are not yet timed?</div><div><br></div><div>I know the tracers take a long time so I turned them off but I still see this discrepancy (plus they should be accounted for under "Postprocessing"). One possible hint is that it seems the "mesh" file is being altered extensively during checkpoints - perhaps this is related?</div><div><br></div><div>Thanks for any ideas,</div><div><br></div><div>-Eric</div><div><br></div></body></html>