Re: Profiling a drag and drop operation
Re: Profiling a drag and drop operation
- Subject: Re: Profiling a drag and drop operation
- From: Michael Ash <email@hidden>
- Date: Fri, 5 Jun 2009 21:40:51 -0400
On Fri, Jun 5, 2009 at 6:56 PM, Tron Thomas<email@hidden> wrote:
> Nick Zitzmann wrote:
>>
>> On Jun 5, 2009, at 4:11 PM, Tron Thomas wrote:
>>
>>> What could allow me to determine why the new program is much slower when
>>> trying to deal with this dropped file?
>>
>>
>> Have you tried reproducing the problem with Shark running and sampling the
>> app? Shark comes with the developer tools, unless you disabled the CHUD
>> installation.
>>
>> Nick Zitzmann
>> <http://www.chronosnet.com/>
>>
>>
> Yes, I had tried a time profile using Shark, delaying the sampling until 5
> seconds after the application started. This allowed me to drop the file
> just after I knew the profiling had begun.
>
> I don't know how well I understand the output I got from it. I found an
> area of my code , shark said was taking up about 4.8%, which was about the
> third highest entry in the results. Despite making that change the
> application, doesn't seem to load the file any faster. Additional Shark
> profiling show that changed code is now longer showing up in the profiling
> results.
I suggest reading this:
http://www.mikeash.com/?page=pyblog/friday-qa-2009-02-06-profiling-with-shark.html
Typically the most common problem with understanding Shark output is
that it defaults to Heavy mode, even though Tree is a lot more
understandable and useful.
Note that your delayed sample trick is unnecessary and potentially
harmful if the sampling goes on for a significant time after your
freeze has stopped. You can start and stop Shark by simply pressing
option-escape, so you can press that as you start your drag, then
again as soon as it unfreezes to ensure that you're only sampling the
right area.
Spin Control is another useful tool here, as it can automatically
start and stop sampling in response to an application no longer
responding to events. Its output is not as comprehensive as Shark's,
but you probably don't need the extra information at this point.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden