site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Aug 28, 2009, at 7:22 PM, Eric Gouriou wrote: Thanks, Joel --- fastest mac firefox! http://wagerlabs.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... 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? This email sent to site_archiver@lists.apple.com