Curtis L. Olson writes: > > Erik Hofman writes: > > Curtis L. Olson wrote: > > > > > True ... what I was trying to communicate is that if something like a > > > property string fetch shows up high in list of time consuming function > > > calls, we don't necessarily know if most of those calls were made > > > during initialization where it doesn't really matter, or during the > > > main loop where it matters a lot more. > > > > This is the top 20 of FlightGear CVS on my O2: > > > > http://www.a1.nl/~ehofman/fgfs/download/usertime.output.gz
You have to let the process run much longer until things like ssgMakeMipMaps don't show up in the top 100 :-) > > The nice thing is that it also contains OpneGL calls. That is good and bad the bad part is that it takes time to instrument the profiling and since we can't do anything about speeding up the low level code why do we want it influencing the run time ?? > Does anyone have any ideas for factoring out the > startup/initialization time from these performance reports? Sure, just let FlightGear run for a minimum of 20 minutes when profilng Cheers Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
