Thanks. I will look into that option.But I can also split my task.And right now
I want to understand the boundaries of a tool. At least approximate.
Original message
From: Konstantin Tokarev
Date: 08/07/2016 13:50 (GMT+02:00)
To: Stepan Zakharov
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
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