intro story Coast / Estuary

Coast / Estuary

Coastal systems are among the most dynamic physical systems on earth and are subject to a large variety of forces. The morphodynamic changes occurring to coastlines worldwide are of great interest and importance. These changes occur as a result of the erosion of sediments, its subsequent transport as bed load or suspended load, and eventual deposition. 
 
Estuaries are partly enclosed water bodies that have an open connection to the coast. Estuaries generally have one or more branching channels, intertidal mudflats and/or salt marshes. Intertidal areas are of high ecological importance and trap sediments (sands, silts, clays and organic matter).
Within the Delft3D modelling package a large variation of coastal and estuarine physical and chemical processes can be simulated. These include waves, tidal propagation, wind- or wave-induced water level setup, flow induced by salinity or temperature gradients, sand and mud transport, water quality and changing bathymetry (morphology). Delft3D can also be used operationally e.g. storm, surge and algal bloom forecasting. 
 
On this discussion page you can post questions, research discussions or just share your experience about modelling coastal and/or estuarine systems with Delft3D FM. 
 

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ
Cohesive sediments & muddy systems

 

 

Message Boards

VERY slow computation!

Erin King, modified 2 Years ago.

VERY slow computation!

Youngling Posts: 12 Join Date: 10/5/16 Recent Posts
Hi,

I have recently started using Delft3D on a new PC which should provide performance gains over my current one. However this has only proved partly true. When running my model domain at 4km wave resolution the performance is better on the new PC. When running at 1km resolution the new PC slows down massively to the point where it is almost 10x slower on the new machine versus the old one! (both running the 1km model).

The idea behind the new PC was partly to allow us to move up to 1km resolution with the waves and so this is a problem.

The slow down appears to be in the Wait (ext. modules) section on the Performance timers output in the tri-diag files (see the images attached). I believe that is just reflecting that the slow down is in the wave computation which is visually apparent watching the iterations.

The new machine has an 8 core CPU with 16 threads VS a 6 core CPU. I have tried reducing the number of threads used by SWAN on the new PC, which speeds up the computation time marginally (enough to run the tests shown in the pictures) but the problem remains.

The new machine is Windows 10 VS Windows 7 on the old machine. Could it be an OS issue?

Any help or experience shared will be appreciated!

Cheers,
Erin