Performance in OpenDrift
Check if OMP_NUM_THREADS is set in a way that restricts the number of cores that can be used.
Some optional packages might increase performance for your use case:
roaring-landmask (pip install roaring-landmask), will save you disk-space and startup-time. Especially if you run many small simulations this can make a big difference.
pykdtree (among other areas this might speed up cartopy and the unstructured readers)
imagemagick (might yield faster gif generation)
Tuning the simulation
OpenDrift is fairly optimised Python code, but simulations may take long time (even several days) if many elements (~millions) and many time steps (~thousands). We hope to parallelise OpenDrift in the near future, to improve performance on machines with many cores. In the meantime, the following can be done to increase performance or decrease memory and disk usage:
Decrease the number of particles to a minimum
Not using as larger time steps than necessary. When calling method
run(), one can specify
time_stepwhich is the internal time step for calculation, and
time_step_outputwhich is the steps at which data are stored in memory (and written to file if
Reduce memory consumption by either:
export_buffer_lengthin run(). 100 is default, but a smaller value may be specified if there are very many elements (~millions)
limit the number of variables saved to disk (and stored in memory) by providing a list of needed variables as the list
export_variableswhen calling run()
Reading data from local files is faster than from remote servers, e.g. Thredds, although the latter is very convenient.
For the 3D models, vertical mixing takes considerable time. If not needed, this can be switched off by setting
An upper limit may be given to the number of iterations per outer timestep, as illustrated in example_long_verticalmixing.py.
The mixing can also be significantly speeded up by using constant TS-profiles during the iterations, by specifying
o.set_config('vertical_mixing:TSprofiles', False)(which is default)
Quasi-parallelisation can be done by splitting the initial elements up in geographical sub-regions, and running simulations in parallel for each subset.
Some notes about performance
Each OpenDrift module has an attribute
max_speed which indicates the maximum velocity that elements will likely encounter. This is accessible as
o.max_speed for an OpenDrift object
o. Typical values are 2 m/s for ocean drift models, but as large as 12 m/s for the WindBlow module where elements move at the speed of the wind. It might be overriden by the user at any time, simply by writing
o.max_speed = 3 before starting a run. This parameter is not an absolute bound for instantaneous velocity, but rather for the average velocity in a particular direction over a time period. It serves two purposes:
During the run, all readers are called to return data (2D or 3D “blocks”) covering all the elements. This block of data should not only cover elements at their present position, but also the area over which elements might move within the next timestep of the reader (e.g. typically 1, 3, 6 or 24 hours for an ocean model). As with the landmask above, this buffer around present positions is calculated as
o.max_speed * timestep_of_reader. Again, it of interest to keep the buffer as small as possible to save time reading data from file (or from Thredds), but still avoiding that elements will leave the reader-block coverage within the timestep.