HPC FAQ: Difference between revisions
Content deleted Content added
No edit summary |
|||
Line 55:
* Be more thorough in reviewing the model results. Although this is best practice for any modelling, it is paramount for unconditionally stable solvers like HPC that thorough checks of the model’s flow patterns, performance at boundaries and links is carried out.
* The CME%, which is an excellent indicator that the Classic 2D solver is numerically converging, is not generally of use for HPC, which is volume conserving and effectively 0% subject to numerical precision. Non-zero whole of model CME% for HPC 1D/2D linked models is usually an indication of either the 1D and 2D adaptive timesteps being significantly different, or a poorly configured 1D/2D link.
= How much is TUFLOW HPC faster than Classic?
This is largely based on hardware that is used to run HPC models (CPU and GPU) and its performance. On average, HPC using GPU hardware runs about 10 times faster than Classic and about 30 times faster than HPC using CPU with two CPU threads (current default is 4). Even though HPC using CPU hardware is in general slower than Classic, more CPU threads can be used to achieve faster run times. As TUFLOW Classic is not parallelised it can only run on one CPU thread and cannot be further improved even with available CPU resources.<br>
= Why is my model using 2020 HPC slower than 2018 HPC?=
| |||