[geos-devel] Upgrading to geos 3.3.0 broke all our codebase !

[Sandro Santilli]

On Fri, Jul 08, 2011 at 05:57:49PM +0200, Maxime van Noppen wrote:
> On 07/08/2011 05:44 PM, Sandro Santilli wrote:
> >You're basically noticing here that about 17 calls to malloc + 17
> >calls to free (34 calls of memory related functions) are taking up
> >41 + 15.2 = 56.2% of the time while 41% of it is spent doing 100000
> >dynamic_cast calls.
> 
> Why only 17 malloc/free? I attach the output of callgrind, which
> shows 100000 calls to dynamic_cast, new and delete.

I said 17 expecting those malloc/free to be due std::vector push_back
which I tought would happen in multiple of two (2^17 > 100000)

> >I guess your average GEOS application does more than that ?
> 
> The application as whole, of course. But this kind of loop on that
> large datasets also exists. Loading data for example, where we have
> a loop akin to that one (except that we dynamic_cast the result of
> reading a WKB, thus reducing it's impact but it's still noticeable
> and enough for us to worry about).

I'd still be interested in those numbers.

--strk;

  ()   Free GIS & Flash consultant/developer
  /\   http://strk.keybit.net/services.html