* Robert -- Thursday 24 March 2011:
> Is event_mgr.cxx the right place to look at?
Well, the main purpose of the event manager is to handle
Nasal's settimer() code. So you better look for slow recurring
Nasal code. You can redefine settimer() and let it output the
time spent. I can't test that at the moment, but it will be
something like this:
var orig_settimer = globals.settimer;
var globals.settimer = func(fn, interval, mode = 0) {
var start = systime();
var where = caller(1);
orig_settimer(fn, interval, mode);
printf("(%.6f) settimer in %s:%s took %.6f s",
start, where[2], where[3], systime() - start);
}
This should show you lines like:
(10.345678) settimer in .../debug.nas:17 took 0.000290 s
(11.345670) settimer in .../screen.nas:68 took 0.004989 s
Then you search for particularly slow execution time and check
if it's in one-second intervals.
m.
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
