[geos-devel] Updated timings/profiling.

[strk at refractions.net]

On Tue, Feb 15, 2005 at 04:30:50PM -0500, Jon Schlueter wrote:
> > First line of flat profile:
> > 
> > Flat profile:
> > 
> > Each sample counts as 0.01 seconds.
> >   %   cumulative   self              self     total
> >  time   seconds   seconds    calls   s/call   s/call  name
> >  15.35     14.27    14.27 45281976     0.00     0.00  geos::STRtree::STRIntersectsOp::intersects(void const*, void const*)
> >   7.73     21.46     7.19                             geos::AbstractSTRtree::query(void const*)
> >   4.28     25.44     3.98    28602     0.00     0.00  geos::RobustLineIntersector::computeIntersect(geos::Coordinate const&, geos::Coordinate const&, geos::Coordinate const&, geos::Coordinate const&)
> >   3.72     28.90     3.46 40923120     0.00     0.00  geos::DefaultCoordinateSequence::add(geos::Coordinate const&)
> > 
> 
> 
> Dumb question (I've been partly following the discussion but not very closely).
> 
> Which functions are the slowest per call?
> 
> are there any optimizations that can reduce the number of Calls to
> these functions?
>          has anyone looked at the complexity of these functions? O(n)
> type analysis?

What you see above is the report of slowest functions.
The '% time' column reports percent of total run time.
'self seconds' are the seconds spent inside that function.
Both values do not contain time spent in child functions.
The first listed runs in constant time.

To see time spent in functions including its childs you have
to look at the call graph. It has not been reported here, but
you can have a feeling of it looking at the attachment I posted
some days ago. Refer to the gprof manual for details:
http://www.gnu.org/software/binutils/manual/gprof-2.9.1/html_mono/gprof.html

--strk;

> 
> Jon Schlueter
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel