|
From: Eric S. <mas...@gm...> - 2011-06-21 13:56:30
|
Hi all Sorry for posting this question again. However, it is rather important for my diploma thesis. What does the x-axis represent exactly when '--time-unit=B' is used together with 'massif' and 'ms_print'? Or is this rather a question related to 'valgrind-developers' mailing list? Please see for the intention of my question the previous post below. Many thanks Eric -------- Original-Nachricht -------- Betreff: [Valgrind-users] Massif: --time-unit=B Datum: Mon, 06 Jun 2011 19:18:12 +0200 Von: Eric Schwarz <mas...@gm...> An: val...@li... Hi all When using 'massif' it is recommended for short programs to use '--time-unit=B' option since o/w no or hardly any output is shown using ms_print for visualisation [1]. My question is now regarding the units of the x-axis. As far as I have understood represents the unit the cumulated number of bytes allocated and freed when option '--time-unit=B' is used. Snapshots are taken for allocations and de-allocations, but also in-between of them. Since the value of the y-axis (Each vertical bar represents a snapshot, i.e. a measurement of the memory usage at a certain point in time. [1]) and the value of the x-axis, which represents the cumulated number of bytes allocated and freed, have a dependency to each other, how is it possible that a parallel line to the x-axis is drawn in the graph [1] since actually only a change in the heap usage should generate a forward move on the x-axis. Hope my problem was described somehow comprehensible. Many thanks for your contributions Eric [1]...http://valgrind.org/docs/manual/ms-manual.html ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Wan M. F. W. I. <wan...@mc...> - 2011-06-21 14:05:09
|
Maybe I'm wrong but in the manual it says that : "...For a short-running program like this, we can use the --time-unit=B option to specify that we want the time unit to instead be the number of bytes allocated/deallocated on the heap and stack(s)...." Which means the time unit is the number of bytes allocated/deallacated on the head __and__ stack. On Tue, Jun 21, 2011 at 3:56 PM, Eric Schwarz <mas...@gm...>wrote: > ** > Hi all > > > Sorry for posting this question again. However, it is rather important for > my diploma thesis. > > What does the x-axis represent exactly when '--time-unit=B' is used > together with 'massif' and 'ms_print'? > > Or is this rather a question related to 'valgrind-developers' mailing list? > > Please see for the intention of my question the previous post below. > > > Many thanks > Eric > > -------- Original-Nachricht -------- Betreff: [Valgrind-users] Massif: > --time-unit=B Datum: Mon, 06 Jun 2011 19:18:12 +0200 Von: Eric Schwarz > <mas...@gm...> <mas...@gm...> An: > val...@li... > > Hi all > > > When using 'massif' it is recommended for short programs to use > '--time-unit=B' option since o/w no or hardly any output is shown using > ms_print for visualisation [1]. > > My question is now regarding the units of the x-axis. > > As far as I have understood represents the unit the cumulated number of > bytes allocated and freed when option '--time-unit=B' is used. > > Snapshots are taken for allocations and de-allocations, but also > in-between of them. > > Since the value of the y-axis (Each vertical bar represents a snapshot, > i.e. a measurement of the memory usage at a certain point in time. [1]) > and the value of the x-axis, which represents the cumulated number of > bytes allocated and freed, have a dependency to each other, how is it > possible that a parallel line to the x-axis is drawn in the graph [1] > since actually only a change in the heap usage should generate a forward > move on the x-axis. > > Hope my problem was described somehow comprehensible. > > > Many thanks for your contributions > Eric > > [1]...http://valgrind.org/docs/manual/ms-manual.html > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is safe, > secure and there when you need it. Discover what all the cheering's about. > Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > Valgrind-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > -- Wan Mohd Fairuz WAN ISMAIL OMAP System Multimedia Integration Team Texas Instrument France +33 (0)4 93 22 20 16 begin_of_the_skype_highlighting +33 (0)4 93 22 20 16 end_of_the_skype_highlighting +33 (0)6 43 46 13 39 begin_of_the_skype_highlighting +33 (0)6 43 46 13 39 end_of_the_skype_highlighting |
|
From: Nicholas N. <n.n...@gm...> - 2011-06-25 21:52:17
|
On Tue, Jun 21, 2011 at 11:56 PM, Eric Schwarz
> When using 'massif' it is recommended for short programs to use
> '--time-unit=B' option since o/w no or hardly any output is shown using
> ms_print for visualisation [1]. My question is now regarding the units of
> the x-axis. As far as I have understood represents the unit the cumulated
> number of bytes allocated and freed when option '--time-unit=B' is used.
> Snapshots are taken for allocations and de-allocations, but also in-between
> of them. Since the value of the y-axis (Each vertical bar represents a
> snapshot, i.e. a measurement of the memory usage at a certain point in time.
> [1]) and the value of the x-axis, which represents the cumulated number of
> bytes allocated and freed, have a dependency to each other, how is it
> possible that a parallel line to the x-axis is drawn in the graph [1] since
> actually only a change in the heap usage should generate a forward move on
> the x-axis.
>
I guess you're talking about this graph:
19.63^ ###
| #
| # ::
| # : :::
| :::::::::# : : ::
| : # : : : ::
| : # : : : : :::
| : # : : : : : ::
| ::::::::::: # : : : : : : :::
| : : # : : : : : : : ::
| ::::: : # : : : : : : : : ::
| @@@: : : # : : : : : : : : : @
| ::@ : : : # : : : : : : : : : @
| :::: @ : : : # : : : : : : : : : @
| ::: : @ : : : # : : : : : : : : : @
| ::: : : @ : : : # : : : : : : : : : @
| :::: : : : @ : : : # : : : : : : : : : @
| ::: : : : : @ : : : # : : : : : : : : : @
| :::: : : : : : @ : : : # : : : : : : : : : @
| ::: : : : : : : @ : : : # : : : : : : : : : @
0 +----------------------------------------------------------------------->KB
^^^^^^^^^
And the horizontal lines, eg. where I've added "^^^" marks below the x-axis?
Those horizontal lines make sense with --time-unit=ms and --time-unit=i.
But you're right that they don't make sense with --time-unit=B. Really,
they should angle up or down.
I'm not inclined to fix it thought; --time-unit=B is really only there to
facilitate regression testing, as it gives more deterministic graphs than
--time-unit=ms or --time-unit=i.
I hope this answers your question!
Nick
Nick
|
|
From: Eric S. <mas...@gm...> - 2011-06-26 10:06:43
|
Hi Nick You have understood perfectly what I have ment. Many thanks for your attendance of my question. Regards Eric Am 25.06.2011 23:51, schrieb Nicholas Nethercote: > On Tue, Jun 21, 2011 at 11:56 PM, Eric Schwarz > > When using 'massif' it is recommended for short programs to use > '--time-unit=B' option since o/w no or hardly any output is shown > using ms_print for visualisation [1]. My question is now regarding > the units of the x-axis. As far as I have understood represents > the unit the cumulated number of bytes allocated and freed when > option '--time-unit=B' is used. Snapshots are taken for > allocations and de-allocations, but also in-between of them. Since > the value of the y-axis (Each vertical bar represents a snapshot, > i.e. a measurement of the memory usage at a certain point in time. > [1]) and the value of the x-axis, which represents the cumulated > number of bytes allocated and freed, have a dependency to each > other, how is it possible that a parallel line to the x-axis is > drawn in the graph [1] since actually only a change in the heap > usage should generate a forward move on the x-axis. > > > I guess you're talking about this graph: > > 19.63^ ### > | # > | # :: > | # : ::: > | :::::::::# : : :: > | : # : : : :: > | : # : : : : ::: > | : # : : : : : :: > | ::::::::::: # : : : : : : ::: > | : : # : : : : : : : :: > | ::::: : # : : : : : : : : :: > | @@@: : : # : : : : : : : : : @ > | ::@ : : : # : : : : : : : : : @ > | :::: @ : : : # : : : : : : : : : @ > | ::: : @ : : : # : : : : : : : : : @ > | ::: : : @ : : : # : : : : : : : : : @ > | :::: : : : @ : : : # : : : : : : : : : @ > | ::: : : : : @ : : : # : : : : : : : : : @ > | :::: : : : : : @ : : : # : : : : : : : : : @ > | ::: : : : : : : @ : : : # : : : : : : : : : @ > 0 +----------------------------------------------------------------------->KB > ^^^^^^^^^ > And the horizontal lines, eg. where I've added "^^^" marks below the > x-axis? > > Those horizontal lines make sense with --time-unit=ms and > --time-unit=i. But you're right that they don't make sense with > --time-unit=B. Really, they should angle up or down. > > I'm not inclined to fix it thought; --time-unit=B is really only > there to facilitate regression testing, as it gives more deterministic > graphs than --time-unit=ms or --time-unit=i. > > I hope this answers your question! > > Nick > > Nick |