[implicit] store Geometry if it is re-used
Since grid implementations like Yasp calculate the Geometries on the fly, every call to entity.geometry() may involve computation. This patch stores a Geometry when it can be used later on in the same block. Only for the implicit models, decoupled contains a lot more. For simple models this actually pays off: for 1p in 3d on a larger grid, the running time could be reduced from 15.5 to 14 s. Reviewed by Timo. git-svn-id: svn://svn.iws.uni-stuttgart.de/DUMUX/dumux/trunk@14284 2fb0f335-1f38-0410-981e-8018bf24f1b0
Showing
- dumux/geomechanics/el1p2c/el1p2clocalresidual.hh 3 additions, 2 deletionsdumux/geomechanics/el1p2c/el1p2clocalresidual.hh
- dumux/geomechanics/el2p/el2plocaloperator.hh 7 additions, 6 deletionsdumux/geomechanics/el2p/el2plocaloperator.hh
- dumux/geomechanics/el2p/el2pmodel.hh 5 additions, 3 deletionsdumux/geomechanics/el2p/el2pmodel.hh
- dumux/implicit/1p2c/1p2cfluxvariables.hh 3 additions, 2 deletionsdumux/implicit/1p2c/1p2cfluxvariables.hh
- dumux/implicit/2pdfm/2pdfmfluxvariables.hh 4 additions, 2 deletionsdumux/implicit/2pdfm/2pdfmfluxvariables.hh
- dumux/implicit/2pdfm/2pdfmlocalresidual.hh 5 additions, 4 deletionsdumux/implicit/2pdfm/2pdfmlocalresidual.hh
- dumux/implicit/2pdfm/2pdfmvolumevariables.hh 4 additions, 3 deletionsdumux/implicit/2pdfm/2pdfmvolumevariables.hh
- dumux/implicit/cellcentered/ccfvelementgeometry.hh 12 additions, 8 deletionsdumux/implicit/cellcentered/ccfvelementgeometry.hh
- dumux/implicit/common/implicitvelocityoutput.hh 7 additions, 5 deletionsdumux/implicit/common/implicitvelocityoutput.hh
Loading
Please register or sign in to comment