395
edits
User talk:Philosopher/Nasal introspection: Difference between revisions
Jump to navigation
Jump to search
m
User talk:Philosopher/Nasal introspection (view source)
Revision as of 21:23, 14 August 2013
, 14 August 2013no edit summary
Philosopher (talk | contribs) mNo edit summary |
|||
| Line 63: | Line 63: | ||
As an aside, I'd use another thread to sort the data prior to writing it to a file - I am getting a bunch of stuff at the beginning of the file that simply doesn't seem very relevant in comparison to the rest. | As an aside, I'd use another thread to sort the data prior to writing it to a file - I am getting a bunch of stuff at the beginning of the file that simply doesn't seem very relevant in comparison to the rest. | ||
: Would my explore.py script help here? You can move it to $FG_HOME, run it, and type "list by number of calls / 20" to get the top 20 most-called functions. It's quite helpful, actually ^.^ [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 21:14, 14 August 2013 (UTC) | : Would my explore.py script help here? You can move it to $FG_HOME (or link -s), run it, and type "list by number of calls / 20" to get the top 20 most-called functions. It's quite helpful, actually ^.^ [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 21:14, 14 August 2013 (UTC) | ||
It's confirmed: As previously suggested, your setupDebugExtras() call results in the entire sim session being profiled, see my earlier comments - ideally, just passing extras to call() should MERELY profile the specified naFunc, nothing else - according to the profile, I am seeing the entire sim session profiled during the run, not just the test func - so that's where all the data and refs are coming from. | It's confirmed: As previously suggested, your setupDebugExtras() call results in the entire sim session being profiled, see my earlier comments - ideally, just passing extras to call() should MERELY profile the specified naFunc, nothing else - according to the profile, I am seeing the entire sim session profiled during the run, not just the test func - so that's where all the data and refs are coming from. | ||
: Oh yeah, sorry, get forgetting to take that out.... Well I do (occasionally) but I put it back in [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 21: | : Oh yeah, sorry, get forgetting to take that out.... Well I do (occasionally) but I put it back in. The question is will developers want to profile everything or use call() to just profile their stuff? (which could end up being hard if there are a lot of settimers/setlisteners involved since each would need to be touched) I do think that profiling everything gives a sort of context and ranking, like I was able to tell that aar.nas was particularly bad, whereas I really wouldn't know what "bad" is. I also would like to see if we ''could'' just profile a whole session. BTW: I can confirm that stats aren't getting printed for the single call(). [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 21:23, 14 August 2013 (UTC) | ||
:: then just make it a variable and use a property switch/listener to make it runtime configurable? | :: then just make it a variable and use a property switch/listener to make it runtime configurable? | ||