[Mono-dev] Profiling with heapshot (only)

[Greg Young]

Likely also noalloc.

Cheers,

Greg

On Tue, Aug 16, 2016 at 1:04 AM, Greg Young <gregoryyoung1 at gmail.com> wrote:
> https://github.com/mono/mono/blob/master/mono/profiler/proflog.c#L4772
>
> Is an option you want. Without the enter/leave hooks are registered
> which has a significant cost.
>
> Not sure if this is the only option or just one of a few (have not
> tested on your use case)
>
> Cheers,
>
> Greg
>
> On Tue, Aug 16, 2016 at 12:57 AM, Chris Swiedler
> <cswiedler at trionworlds.com> wrote:
>> I'm trying to use the heapshot=ondemand feature of the logging profiler. I want to turn off all of the other features of the logging profiler, since the allocation/method tracing stuff runs too slow to be useful in the situation that I need to test. However, even with a command line like this:
>>
>> mono-sgen --debug --profile=log:heapshot,heapshot=ondemand,time=fast,port=7103,output=%p.mlpd
>>
>> ...I still get extremely high CPU usage in my apps. From what I understand of the heapshot part of the profiler, it shouldn't need to incur any overhead except when generating the heapshot file. Is there any way to reduce the runtime overhead when it's not generating a heapshot? This link suggests that I should disable counters, but I don't see any options for that:
>>
>> http://mono.1490590.n4.nabble.com/Problems-with-mono-log-pofiler-td4665572.html
>>
>> thanks,
>> chris
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.dot.net
>> http://lists.dot.net/mailman/listinfo/mono-devel-list
>
>
>
> --
> Studying for the Turing test



-- 
Studying for the Turing test