Re: where does initialization time go?
Re: where does initialization time go?
- Subject: Re: where does initialization time go?
- From: Joel Reymont <email@hidden>
- Date: Fri, 28 Aug 2009 21:10:07 +0100
On Aug 28, 2009, at 7:22 PM, Eric Gouriou wrote:
dtrace uses fork/exec or posix_spawn (I didn't check which one),
while a typical launch
(Dock, Finder, open) uses LaunchServices.
I'd recommend reworking your script to watch the exec-success of
firefox-bin and use
a static probe (no need for $target then) to mark the end time.
Then you can use a more normal
launch method, for example open .../Minefiled.app .
I'll fix my scripts. I already have a static probe, e.g.
mozilla:::main-entry. I was mistakenly using it with $target.
- Using a SSD to measure cold launch is not representative of a
typical user.
A cold launch using a SSD is much closer to a warm launch using a
good old mechanical
hard drive. Optimizing this scenario will not necessarily improve
the experience of your users.
I don't think switching to a slower drive is an option for me. Well,
it's an option but I hate to entertain it! I think I'll just try to
have the times I get, for example, with the hope that they will be
halved for other users as well.
What about my "dynamic linking time doesn't matter" thesis? Should I
chalk 9 seconds to DTrace overhead?
Thanks, Joel
---
fastest mac firefox!
http://wagerlabs.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden