[geos-devel] JTS/GEOS performance - smart-ptr vs ref counting

[Martin Davis]

Something to note here is that the original profiling numbers given by
strk were based on the buffer algorithm.  Buffer is by far the most
complex algorithm in JTS, and inherently has to create lots of new
coordinate sequences (amongst other things).  There may be no way to
remove this requirement, in which case the only way to improve the speed
is to increase the speed of memory allocation.

Martin Davis, Senior Technical Architect
Vivid Solutions Inc.      www.vividsolutions.com
Suite #1A-2328 Government Street Victoria, B.C. V8T 5G5
Phone: (250) 385 6040 - Local 308 Fax: (250) 385 6046


> -----Original Message-----
> From: Norman Vine [mailto:nhv at cape.com] 
> Sent: January 31, 2005 4:52 PM
> To: GEOS Development List
> Subject: RE: [geos-devel] JTS/GEOS performance - smart-ptr vs 
> ref counting
> 
> 
> Martin Davis writes:
> > 
> > 
> > That was pretty much my point - smart pointers alone don't produce 
> > memory efficiency, they just make the code safer (and hopefully 
> > easier).
> 
> Well they are a little faster then any garbage collection 
> routine could ever be but you are right 'speed issues' aren't 
> why they are used.
> 
> Has anyone profiled the code recently,  without profiling 
> statistics optimization discussions are really just guesswork.
> 
> Norman 
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net 
> http://geos.refractions.net/mailman/listinfo/geos-devel
>