On Sat, Jun 6, 2009 at 3:03 AM, Wade Tregaskis wrote:
>> 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.
>
> The two modes are good for different things. Heavy view is more intuitiv
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 pr
On Fri, Jun 5, 2009 at 6:56 PM, Tron Thomas 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 w
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
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 d
