From: Kristen Accardi <kaccardi@gmail.com>
To: Chris Mason <clm@fb.com>, David Woodhouse <dwmw2@infradead.org>
Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] benchmarking and performance trends
Date: Wed, 15 Jul 2015 20:32:34 +0000 [thread overview]
Message-ID: <CAH3eK3SaKyYkrYyRGj2o6SGc+_DqPGjef1+bm8TWL-xbCfbPfg@mail.gmail.com> (raw)
In-Reply-To: <20150715195837.GA14507@ret.masoncoding.com>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
On Wed, Jul 15, 2015 at 12:58 PM Chris Mason <clm@fb.com> wrote:
> On Wed, Jul 15, 2015 at 08:39:55PM +0100, David Woodhouse wrote:
> > On Wed, 2015-07-15 at 19:23 +0000, Kristen Accardi wrote:
> > > I am very interested to hear what if any benchmarks people are doing
> > > on non-server platforms as well. I find it difficult to know what
> > > benchmarks customers think are important for upstream linux for
> > > desktop and mobile systems that are not running Android or Chrome,
> > > and would love to hear what others are using.
> >
> > I would imagine the most interesting metrics are all about power vs.
> > performance, rather than pure performance.
> >
> > In fact, in the server environment where you have to pay for the power
> > in the first place, and then pay again for the air conditioning to
> > extract the resulting heat, I'm surprised it isn't already more of a
> > consideration.
>
> 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.
>
> -chris
>
>
Artem has setup this capability with 2 server benchmarks (specpower and
specweb) and has been taking a look at upstream kernel PnP with regard to
these benchmarks on specific intel platforms.
[-- Attachment #2: Type: text/html, Size: 1829 bytes --]
next prev parent reply other threads:[~2015-07-15 20:32 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 [this message]
2015-07-17 19:38 ` Artem Bityutskiy
2015-07-16 1:35 ` Len Brown
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=CAH3eK3SaKyYkrYyRGj2o6SGc+_DqPGjef1+bm8TWL-xbCfbPfg@mail.gmail.com \
--to=kaccardi@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=clm@fb.com \
--cc=dwmw2@infradead.org \
--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