On Dienstag, 12. Juli 2016 14:23:13 CEST Josef Weidendorfer wrote:
> Am 08.07.2016 um 01:03 schrieb Stepan Zakharov:
> > Hello,
> > If I remember correct, callgrind takes x30 overhead in general (when I
> > was running it). Usually , I had to run it on small tasks that won't
> > take more then a fe
Am 08.07.2016 um 01:03 schrieb Stepan Zakharov:
> Hello,
> If I remember correct, callgrind takes x30 overhead in general (when I
> was running it). Usually , I had to run it on small tasks that won't
> take more then a few minutes, so this was not a bother to me.
>
> But right now I am wonering if
On Fri, 2016-07-08 at 14:38 +0300, Stepan Zakharov wrote:
> Thanks. I will look into that option.
Yes, callgrind and kcachegrind are very easy to use/very precise/...,
but the price to pay is the slowness.
Other profilers having much less overhead might be good enough.
> But I can also split my ta
@lists.sourceforge.net
Subject: Re: [Valgrind-users] Callgrind longest possible run
08.07.2016, 02:04, "Stepan Zakharov" :
> Hello,
> If I remember correct, callgrind takes x30 overhead in general (when I was
> running it). Usually , I had to run it on small tasks that won't take mo
08.07.2016, 02:04, "Stepan Zakharov" :
> Hello,
> If I remember correct, callgrind takes x30 overhead in general (when I was
> running it). Usually , I had to run it on small tasks that won't take more
> then a few minutes, so this was not a bother to me.
>
> But right now I am wonering if I ca
