20,741
edits
User talk:Philosopher/Nasal introspection: Difference between revisions
Jump to navigation
Jump to search
User talk:Philosopher/Nasal introspection (view source)
Revision as of 21:29, 14 August 2013
, 14 August 2013→August 14
m (→August 14) |
|||
| Line 70: | Line 70: | ||
: 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) | : 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) | ||
::: Yeah, completely agreed - ideally, we really WANT the full session to be profiled, but obviously there are still some issues, so we should slow down a second and fix the call() implementation first to be able to profile individual scripts. That would give us an idea about what's going on - profiling the whole session is still too massive timing/memory-wise, so that we need to use call() as a testbed to understand what's happening before we can look again at profiling the entire sim session, which I also consider a primary goal. Regarding listeners and timers, I think we could patch the FG side of things to "inherit" extras based on the initial call().--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 21:29, 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? | ||