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 can measure the entire life-span of critical
stages in our application. Usually, it takes up to 20 hours to perform a load
test. And I would like to measure that period. For callgrind it means to run
20x30=600hrs. Which is 25 days. Is it really possible to run and record for
such a long time? I heard the Counters in CallGrind are 64-bit so this part
should not be the problem, but what I'm worrying about is the RAM overhead. It
will kinda need to store all the upcoming dump in memory, isn't it? How much
big will it be? And if so, will the CallgrindAnnotate or graphical tool (forgot
the name) accept to proccess such a big dump?So, basically, these are my
questions. Will be very grateful if you could enhance my knowledge about the
capabilities of the tool.Best, Stepan
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
