Re: Shark - where is application spending most of the time?
Re: Shark - where is application spending most of the time?
- Subject: Re: Shark - where is application spending most of the time?
- From: Izidor Jerebic <email@hidden>
- Date: Wed, 23 Jun 2004 21:19:53 +0200
On 23 Jun 2004, at 20:25, Shawn Erickson wrote:
To get function run times, run rates, and related metrics you need to
instrument the application at compile time. This instrumentation
facility is provided by the GCC compiler/tool chain and is what gprof
and Saturn use. The Saturn documentation tells you how to configure
build options to instrument you application so you can use those
tools.
Make sure you understand what the tools are telling you before using
any results from them.
Well, I can't use Saturn because it requires instrumented system
libraries, which do not exist right now. I could use gprof, but it is
quite time-consuming.
During development, if speed becomes an obvious issue, I need just
approximate feel of the application. Then I look at the source to see
if I can improve it or I should wait until later stage (because further
development may cause large changes and optimization would not matter).
Shark was quite enough for me until now.
With Shark I can sample my application just about any time and just
about any usage-pattern, so I can be much more productive. If I had to
go through gprof sequence every time, I would probably not do any
profiling yet.
When (if) I need to do fine-grain optimization, I will probably use
gprof. But for now, Shark is quite enough (with the added "cumulative
heavy" view, naturally :-). It helped me spot the most time-consuming
part of my application and replace it with something more efficient...
izidor
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.