[geos-devel] Re: [GEOS] #540: C-API: Allow passing custom memory managment functions

GEOS geos-trac at osgeo.org
Sat May 5 09:42:11 PDT 2012

#540: C-API: Allow passing custom memory managment functions
 Reporter:  strk         |       Owner:  geos-devel@…              
     Type:  enhancement  |      Status:  new                       
 Priority:  major        |   Milestone:  3.4.0                     
Component:  Default      |     Version:  svn-trunk                 
 Severity:  Unassigned   |    Keywords:                            

Comment(by strk):

 I wouldn't be too much concerned about system vs. postgresql, things
 shouldn't get worst than they are in that respect. What concerns me more
 is speed. My early tests show that allocation functions are called _a_lot_
 for very small amount of bytes (often 4!). Didn't test the actual effects
 of using palloc and friends about that.

 Oh, another thing is that alloc/dealloc callbacks can't be per-thread, but
 we can't do much about it.

 Hey, aren't the above limitation minor for the plus of possibly
 interrupting an ST_Buffer ?

Ticket URL: <http://trac.osgeo.org/geos/ticket/540#comment:2>
GEOS <http://geos.refractions.net/>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite (JTS).

More information about the geos-devel mailing list