Revision as of 15:37, 30 January 2026 view source Emilie Nielsen (talk \| contribs) Administrators 6,282 edits →Must TUFLOW users on Linux use the command line interface? ← Older edit		Revision as of 15:48, 3 February 2026 view source Emilie Nielsen (talk \| contribs) Administrators 6,282 edits →Why use TUFLOW on Linux at all? Newer edit →
Line 33: '''Performance'''<br/> Servers or workstations that are dedicated for the running of models can be configured to run TUFLOW and the necessary supporting software (e.g. CodeMeter, NVIDIA GPU drivers, etc.) and very little else, using Linux. There may also be small performance differences in general between an executable built and optimised for Windows or Linux. '''Infrastructure cost'''<br/> Especially relevant when running virtual machines dedicated to running TUFLOW, or many of those in the cloud, most distributions of Linux do not require a licence whereas Windows does. This can substantially reduce the cost of infrastructure. *'''HPC tooling'''<br/> Automation of running TUFLOW models across many computers or in the cloud can be greatly simplified with tooling designed for that purpose. Many such tools are available "off the shelf", but mostly on Linux. (e.g. SLURM, PBS/Torque, etc.). Similarly, containerisation (e.g. Docker, Podman, LXC) typically requires running on Linux as well. : ''Note:'' HPC tooling refers to job scheduling and automation software for managing large numbers of model runs. Containerisation packages applications and their dependencies into portable and reproducible runtime environments. </ol>

TUFLOW on Linux: Difference between revisions