This is my overwhelming concern:
./d firefox-bin startup.d stop-js.d
dtrace -Zqw -x dynvarsize=64m -x evaltime=preinit -p 26713 -s
startup.d -s stop-js.d -s sigcont.d
Total: 5080.276518ms
The only difference between the timing above and the one below is that
I'm not using menu-construct.d.
My apologies for repeating the question but should I view 6.4350621ms/
3.4218030ms as a percentage of startup time without the overhead of
the measuring script or as a percentage of total time using it?
The difference to whether or not I should optimize the timed piece of
code is, obviously, huge!
Thanks, Joel
On Sep 9, 2009, at 9:56 PM, Joel Reymont wrote:
This is another variation, a simpler one...
./d firefox-bin menu-construct.d startup.d stop-js.d
dtrace -Zqw -x dynvarsize=64m -x evaltime=preinit -p 26656 -s menu-
construct.d -s startup.d -s stop-js.d -s sigcont.d
elapsed: 6.4350621ms
cpu : 3.4218030ms
count : 20 times
Total: 19000.464337ms
Total is printed by startup.d [1] whereas the rest is from menu-
construct.d [2].
Should I evaluate elapsed time printed by menu-construct.d as a
percentage of total elapsed time printed by startup.d?
---
fastest mac firefox!
http://wagerlabs.com
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
