From: Len Brown <lenb@kernel.org>
To: Chris Mason <clm@fb.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] benchmarking and performance trends
Date: Wed, 15 Jul 2015 21:35:51 -0400 [thread overview]
Message-ID: <CAJvTdKk--RBxhzqCem+O75pWRmi5XWLbbUmypQEPaSaPqcR5CA@mail.gmail.com> (raw)
In-Reply-To: <20150715195837.GA14507@ret.masoncoding.com>
> It would be fun to use turbostat or a rack power meter to
> measure/compare power usage between two kernels in a given benchmark. I
> think the power meters we do have are not going to be fine grained
> enough to give valid results, but if turbostat is consistent enough we
> could try it.
The RAPL power meters exported by turbostat can correlate surprisingly
well with highly accurate external power meters. But even if perfect,
RAPL doesn't know about
the hardware outside of the processor package (except Xeon DRAM), so
the absolute
numbers will not match an AC power meter. But differences are visible
and consistent.
The accuracy and the quality of correlation with actual electricals
varies a lot with
the type of processor. In general, Xeon is the best, followed by
desktop/mobile core,
and Atom's RAPL power meters have been the least accurate of those
shipped, so far.
Yes, 0-day is using this output today to identify regressions, without
any external power meters. But they are also adding external power meters.
There are also systems with instrumented power supplies which export
the system AC power via IPMI.
cheers,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-07-16 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 15:37 Chris Mason
2015-07-15 19:23 ` Kristen Accardi
2015-07-15 19:39 ` David Woodhouse
2015-07-15 19:58 ` Chris Mason
2015-07-15 20:32 ` Kristen Accardi
2015-07-17 19:38 ` Artem Bityutskiy
2015-07-16 1:35 ` Len Brown [this message]
2015-08-02 11:49 ` Fengguang Wu
2015-07-17 21:22 ` Davidlohr Bueso
2015-08-03 4:58 ` Fengguang Wu
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=CAJvTdKk--RBxhzqCem+O75pWRmi5XWLbbUmypQEPaSaPqcR5CA@mail.gmail.com \
--to=lenb@kernel.org \
--cc=clm@fb.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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