• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: where does initialization time go?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: where does initialization time go?


  • Subject: Re: where does initialization time go?
  • From: Eric Gouriou <email@hidden>
  • Date: Fri, 28 Aug 2009 16:55:05 -0700


On Aug 28, 2009, at 3:05 PM, Joel Reymont wrote:
On Aug 28, 2009, at 7:22 PM, Eric Gouriou wrote:
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 .

./cold.sh firefox-bin startup.d stop-main.d
dtrace -Zqw -x dynvarsize=64m -x evaltime=exec -p 35209 -s sigcont.d -s startup.d -s stop-main.d
kill -CONT 35209
Total: 2000.401494ms

[... very complex multi-dtrace script setup ...]

I don't understand why you'd have to go through all this trouble.

mozilla$target:::main-entry
{
exit(0);
}

Note that stop-main.d does not work without $target, even though main-entry is a USDT probe.

mozilla*:::main-entry ? I am not very familiar with creating USDT probes. This might
help if you haven't seen it: <http://blogs.sun.com/dap/entry/writing_a_dtrace_usdt_provider >


This could just be an issue of making sure that dtrace has learned about your provider
by the time it parses the probe definition.


--------------------------------
provider mozilla {
       probe main__entry(void) : (void);
};

proc:::exec-success
/ execname == "firefox-bin" && mpid == 0 /
{
 mstart = timestamp;
 mpid = pid;
}

mozilla*:::main-entry
/ pid == mpid /
{
 mend = timestamp;
 printf("Total: %u ms\n", (mend - mstart)/1000000);
 exit(0);
}
--------------------------------

sudo dtrace -s ...   &
sleep 5
open .../Minefield.app

  Eric


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
  • Follow-Ups:
    • Re: where does initialization time go?
      • From: Joel Reymont <email@hidden>
References: 
 >dyld cache: shared_region_roots/Applications.paths (From: Joel Reymont <email@hidden>)
 >Re: dyld cache: shared_region_roots/Applications.paths (From: Joel Reymont <email@hidden>)
 >Re: dyld cache: shared_region_roots/Applications.paths (From: Jean-Daniel Dupas <email@hidden>)
 >Re: dyld cache: shared_region_roots/Applications.paths (From: Joel Reymont <email@hidden>)
 >Re: dyld cache: shared_region_roots/Applications.paths (From: Jonas Maebe <email@hidden>)
 >where does initialization time go? (From: Joel Reymont <email@hidden>)
 >Re: where does initialization time go? (From: Eric Gouriou <email@hidden>)
 >Re: where does initialization time go? (From: Joel Reymont <email@hidden>)

  • Prev by Date: Relating dtrace thread ids to Java threads
  • Next by Date: Re: where does initialization time go?
  • Previous by thread: dtrace and missing a good chunk of startup time
  • Next by thread: Re: where does initialization time go?
  • Index(es):
    • Date
    • Thread