[Dune] Returning Geometries As Objects
Martin Nolte
nolte at mathematik.uni-freiburg.de
Wed Jan 25 13:47:54 CET 2012
Hi Jö,
the Geometry for SPGrid is actually stored in the Geometry object. The first
naive implementation resulted in a slight performance penalty, but by now I'm
down to 29.6s again. For the other grids: Yes, the geometry is stored as a
reference.
Moreover, I don't think that this test would change a lot if the geometry were
actually returned, because the geometry is only fetched once (finitevolume
example from dune-grid-howto). But feel free to test it (I guess GeometryGrid
would be a good candidate).
Best,
Martin
On 01/25/2012 01:36 PM, Jö Fahlke wrote:
> Am Wed, 25. Jan 2012, 09:49:01 +0100 schrieb Martin Nolte:
>> I also did some performance tests with gcc-4.6 (my usual explicit
>> finite volume scheme from the dune-grid-howto - slightly adapted for
>> performance measurements):
>>
>> Grid trunk (r7850) branch (r7845)
>> SPGrid 28.945s 31.448s
>> IdGrid<SPGrid> 39.527s 35.848s
>>
>> YaspGrid 43.394s 43.021s
>> IdGrid<YaspGrid> 80.378s 76.978s
>>
>> ALUCubeGrid 247.227s 238.604s
>> IdGrid<ALUCubeGrid> 275.215s 273.532s
>>
>> SGrid 225.179s 207.103s
>> IdGrid<SGrid> 257.393s 217.859s
>
> Since StoreGeometryReference default to true, I assume these were all done
> with an implementation according to (b) (keep a reference to the
> implementation). Are there any timings available with an implementation
> according to (a) (*store* the actual implementation in the geometry object)?
>
> Thanks,
> Jö.
>
--
Dr. Martin Nolte <nolte at mathematik.uni-freiburg.de>
Universität Freiburg phone: +49-761-203-5630
Abteilung für angewandte Mathematik fax: +49-761-203-5632
Hermann-Herder-Straße 10
79104 Freiburg, Germany
More information about the Dune
mailing list