Re: [Pyobjc-dev] Startup time woes

[Just v. R. <ju...@le...>]

Just van Rossum wrote:

> Jack Jansen wrote:
> 
> > If running the profiler is difficult you could start with a ktrace
> > (which is supported since 10.2, yeah!). Start python, in another
> > window do "ktrace -p pid", do the Python bits you're interested in
> > and then do "ktrace -C". You'll only get a system call trace, but if
> > you show it with "kdump -T" you'll get timestamps and it may give an
> > idea where the time is going.
> 
> Hm, since this is about the startup time of an app bundle, I don't
> see how to get the pid in time to start ktrace. Hm, maybe the app
> should do something like os.system("ktrace -p %s" % os.getpid())?
> Would that work? After reading the man page: yeah, should work, -f
> <outfile> should come in handy.

Btw. this works great, except there's no way I can make any useful
judgment from the output :-( There's a _lot_ of stuff goin on. There are
lots of stats calls and other file system operations, so I'm it looks
like we can at least partly blame the sluggishness of HFS+ :-( Still, a
startup time of 3 seconds (let alone 10 with Python 2.2) for a trivial
app with one trivial window is not really a great selling point :-(

Is anyone using UFS and HFS side-by-side to see how much the file system
playes a role here? (This is assuming UFS is indeed much faster than
HFS+ on OSX, don't know how true that is.)

Just