Flood Modeller-TUFLOW Benchmarking: Difference between revisions

Content deleted Content added
Line 17:
 
==Model 1==
The first simulated model was a 287 node Flood Modeller Pro network coupled with a TUFLOW model comprising of 297,746 cells with a 2m resolution. The input boundaries corresponded to a 100 year return period. The model was run for 10 hours of hydrograph time.
 
The models were run on a number of different setups and run for 45 scenarios. The 45 scenarios are as follows:
 
*TUFLOW Classic with a fixed timestep of 0.5 seconds
*TUFLOW HPC run on 2 Cores
Line 27 ⟶ 29:
The TUFLOW version used for the simulations was the 2018-03-AC release and Flood Modeller 4.4.
 
The results of the benchmarking of model 1 are shown in Table x1. The implicit TUFLOW Classic scheme is comparable to the TUFLOW HPC when it is run on a couple of cores. This is due to the smaller timestep used in the explicit finite volume scheme which uses an adaptive timestep. As the number of cores used increases, the linked Flood Modeller Pro-TUFLOW HPC simulation is quicker, with run times reduced by 42%.
A GPU card is essentially made up of a number of cores which can be utilized to undertake the 2D calculations. Running the same model on a GPU card leads to up to an 83% reduction in run times. This means that nearly 8 simulations can be run on a GPU card in the time that a single simulation could be run using TUFLOW classic.
 
A GPU card ishas essentiallya madesignificant upnumber of acores numberwithin of coresit which can be utilized to undertake the 2D calculations. Running the same model on a GPU card leads to up to an 83% reduction in run times. This means that nearly 8 simulations can be run on a GPU card in the time that a single simulation could be run using TUFLOW classic, highlighting the efficiencies of investing in hardware and also GPU modules.
 
==Model 2==