Re: Shark attributing time oddly to source
Re: Shark attributing time oddly to source
- Subject: Re: Shark attributing time oddly to source
- From: Benson Margulies <email@hidden>
- Date: Mon, 13 Apr 2009 21:40:57 -0400
Oddly, while Rick's post helped me see what's slow about this code, it
doesn't explain much about the results themselves. The function in
question really distributed all of its time to a set of static
functions called by function pointer, and so certainly not inlined.
None of them show up in the profile at all.
I replaced the function pointery with calls to inlinable functions.
And now I'm a bit stumped because Shark has cached an old copy of the
source somewhere and I don't know how to get it to see the current
source.
On Mon, Apr 13, 2009 at 9:29 PM, Greg Guerin <email@hidden> wrote:
> Rick Altherr wrote:
>
>> - This function is called _very_ frequently but isn't inlined. Thus, the
>> time spent on the return is actually time spent in the epilog of the
>> function. You options are to reduce the number of calls to the function or
>> to inline it.
>> - The function runs very quickly but is also called frequently. In this
>> case, Nyquist might require a faster sampling rate. The default is 1ms, but
>> 100us is still reasonable. If the profile changes when using 100us, you were
>> seeing aliasing.
>
> Or maybe if the function is approximately synchronized to the sampling
> timer?
>
> -- GG
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden