Skip to content
Snippets Groups Projects
Select Git revision
  • feature/composite-scheme-sources
  • feature/composite-scheme-other-fluxes
  • feature/serraille
  • feature/variational-hydro
  • develop default protected
  • feature/composite-scheme
  • hyperplastic
  • feature/local-dt-fsi
  • feature/kinetic-schemes
  • feature/polynomials
  • feature/gks
  • feature/implicit-solver-o2
  • feature/coupling_module
  • feature/implicit-solver
  • feature/merge-local-dt-fsi
  • master protected
  • feature/escobar-smoother
  • feature/hypoelasticity-clean
  • feature/hypoelasticity
  • feature/Navier-Stokes
  • v0.5.0 protected
  • v0.4.1 protected
  • v0.4.0 protected
  • v0.3.0 protected
  • v0.2.0 protected
  • v0.1.0 protected
  • Kidder
  • v0.0.4 protected
  • v0.0.3 protected
  • v0.0.2 protected
  • v0 protected
  • v0.0.1 protected
32 results

test_MeshDataBase.hpp

Blame
    • Stéphane Del Pino's avatar
      54907ae7
      Add mesh database infrastructure · 54907ae7
      Stéphane Del Pino authored
      The database is just populated with a small 3d cartesian grid which is
      still inaccessible.
      
      This is just a proof of concept: the mesh is build for both `unit_tests`
      and `mpi_unit_tests`.
      
      The optimization resulting from the previous is already noticed even
      with Release build type.
      
      Using `ctest` (old `make test`) one gets the following execution times
      - without mesh building: 3s
      - with a simple mesh building: 31s
      
      Using the new `test` target one gets the following execution times
      - without mesh building: 1.3s
      - with a simple mesh building: 2.7s
      
      (the `make test` results are actually obtained using `ninja` since the
      test is so fast that the majority of the spent time using `make` is
      spent computing target dependencies)
      
      Using `make test` with the new `test` target one gets the following
      execution times
      - without mesh building: 1.95s
      - with a simple mesh building: 3.45s
      54907ae7
      History
      Add mesh database infrastructure
      Stéphane Del Pino authored
      The database is just populated with a small 3d cartesian grid which is
      still inaccessible.
      
      This is just a proof of concept: the mesh is build for both `unit_tests`
      and `mpi_unit_tests`.
      
      The optimization resulting from the previous is already noticed even
      with Release build type.
      
      Using `ctest` (old `make test`) one gets the following execution times
      - without mesh building: 3s
      - with a simple mesh building: 31s
      
      Using the new `test` target one gets the following execution times
      - without mesh building: 1.3s
      - with a simple mesh building: 2.7s
      
      (the `make test` results are actually obtained using `ninja` since the
      test is so fast that the majority of the spent time using `make` is
      spent computing target dependencies)
      
      Using `make test` with the new `test` target one gets the following
      execution times
      - without mesh building: 1.95s
      - with a simple mesh building: 3.45s