From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: liu.ming50@gmail.com
Cc: Ming Liu <peter.x.liu@external.atlascopco.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] buildstats.sh: add ELAPSED option
Date: Tue, 06 Jun 2017 09:20:10 -0500 [thread overview]
Message-ID: <1496758810.26945.120.camel@linux.intel.com> (raw)
In-Reply-To: <1496719226-3132-1-git-send-email-liu.ming50@gmail.com>
On Tue, 2017-06-06 at 05:20 +0200, liu.ming50@gmail.com wrote:
> From: Ming Liu <peter.x.liu@external.atlascopco.com>
>
> This allows users to be able to get the elapsed time of specific
> tasks from buildstats, sometimes could be useful.
>
> Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com>
> ---
> scripts/contrib/bb-perf/buildstats.sh | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/scripts/contrib/bb-perf/buildstats.sh b/scripts/contrib/bb-perf/buildstats.sh
> index 8d7e248..caf34a6 100755
> --- a/scripts/contrib/bb-perf/buildstats.sh
> +++ b/scripts/contrib/bb-perf/buildstats.sh
> @@ -40,6 +40,7 @@
>
> # Stats, by type
> TIME="utime:stime:cutime:cstime"
> +ELAPSED="Started:Ended:Elapsed time"
This is useful, thanks. Just keep in mind that this is not wall time:
these timestamps come from the bitbake engine (not from /proc/[PID]),
which depending on the build parallelisms, times can change.
Leo
> IO="IO wchar:IO write_bytes:IO syscr:IO read_bytes:IO rchar:IO syscw:IO cancelled_write_bytes"
> RUSAGE="rusage ru_utime:rusage ru_stime:rusage ru_maxrss:rusage ru_minflt:rusage ru_majflt:\
> rusage ru_inblock:rusage ru_oublock:rusage ru_nvcsw:rusage ru_nivcsw"
> @@ -113,6 +114,9 @@ for stat in ${STATS}; do
> TIME)
> stats="${stats}:${TIME}"
> ;;
> + ELAPSED)
> + stats="${stats}:${ELAPSED}"
> + ;;
> IO)
> stats="${stats}:${IO}"
> ;;
> --
> 2.7.4
>
prev parent reply other threads:[~2017-06-06 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 3:20 [PATCH] buildstats.sh: add ELAPSED option liu.ming50
2017-06-06 14:20 ` Leonardo Sandoval [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1496758810.26945.120.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=liu.ming50@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.x.liu@external.atlascopco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox