On Thu, 2008-01-10 at 11:33 -0800, Ben Jackson wrote: > On Thu, Jan 10, 2008 at 07:15:46PM +0000, Peter Clifton wrote: > > > > Clearly the "intersect" routine is consuming the most here, with 58% of > > of the profile time in THIS function. Cumulatively, (that is including > > any functions called FROM "intersect", it is 78% of profile time. > > > > Anyway... looks like there is an obvious place to start hacking. > > I disagree for two reasons: An innermost function like this being > called many, many times is represented disproportionately in profiling > output due to profiling overhead. Also, the problem is really that it > is being called too many times. If you fix that, it won't matter how > fast it is individually.
You are of course right.. this is only the place to start hacking IF it isn't called more times than is absolutely needed. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
