Insitu Visualisation time measurements
Run time comparison of simulation with and without insitu visualisation.
- hydrothermal process on fractured cube (coarsest resolution)
number of runs | min time [s] | mean time [s] | max time [s] | |
---|---|---|---|---|
Insitu visualisation | 20 | 64.967 | 68.393 | 79.162 |
without Insitu visualisation | 100 | 59.981 | 61.102 | 66.936 |
post processing | 10 | 56.904 | 57.094 | 57.346 |
Remark
- There are a number of insitu visualisation related warning outputs:
[pvbatch ] vtkMappedDataArray.txx:47 WARN| N7MeshLib31VtkMeshNodalCoordinatesTemplateIdEE (0x55dd110f5ab0): GetVoidPointer called. This is very expensive for vtkMappedDataArray subclasses, since the scalar array must be generated for each call. Consider using a vtkTypedDataArrayIterator instead.
Fixing this warning would improve runtime. cc @bilke
Comparison conditions
- Version: 6.3.2-479-g0f6fe3b1.
- Platform: envinf1, arch linux,
/opt/paraview