trace statements and “omit trace statements”
July 8th, 2005 by Scott Janousek
(No Ratings Yet)
Loading ...1. I seem to recall that -not- omitting tracements can have a slight performance hit when running within the flash player (having hundreds to thousands of traces) … can anyone confirm or deny this??
If it does impact the player, how big of deal is it? I’m sure we all sometimes forget to omit trace statements before a final deploy and I’m curious to know what the impact is, if any at all.
I usually stick to using a custom trace that can be toggled (or a custom log class if it’s an AS 2 project) … however, sometimes I throw in trace statements for quick debugging purposes …
2. If #1 is true, for the flashlite team … does this have a noticable effect in the FL player??
Print This Post
July 9th, 2005 at 7:16 pm
Problably webplayer (or SAplayer -not-debug-version-) doesn’t support “trace” function, BUT, there is such call in bytecode, so “trace()” statement must be performed (even if this nonexistent function).
July 10th, 2005 at 5:14 pm
Just curious … and more so for the Flash Lite player since that’s where performance might be effected (lower processor power/memory, etc) …
Again we’re probably talking hundreds of trace statements before
it starts to have an impact, but still … maybe I’ll whip up a quick test …
July 11th, 2005 at 4:19 pm
probably trace() has less of a performance effect than any custom logging code you may have.