#854 Improve performance of MCMGMapper
Metadata
| Property | Value |
|---|---|
| Reported by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
| Reported at | Dec 13, 2010 12:13 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
| Last edited at | Nov 5, 2013 20:58 |
| Closed by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
| Closed at | Nov 5, 2013 20:58 |
| Closed in version | Unknown |
| Resolution | Implemented |
| Comment | Merged to master in …ca709f81aca. Thanks to Martin and Steffen for their ideas, support, and help. |
Description
The finite volume example from the dune-grid-howto can be sped up by more than 5% using the attached version of the MCMGMapper. This implementation uses arrays to store the offsets based on the topololgyId (with a special treatment for none).
The question is whether we want to merge this into the trunk, since the implementation is not well tested, yet. Additionally, about 5% performance in an explicit finite volume scheme might not be enough reason for some people. Opinions?