All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Kristen Accardi <kaccardi@gmail.com>, Chris Mason <clm@fb.com>,
	David Woodhouse <dwmw2@infradead.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] benchmarking and performance trends
Date: Fri, 17 Jul 2015 22:38:22 +0300	[thread overview]
Message-ID: <1437161902.14756.15.camel@linux.intel.com> (raw)
In-Reply-To: <CAH3eK3SaKyYkrYyRGj2o6SGc+_DqPGjef1+bm8TWL-xbCfbPfg@mail.gmail.com>

On Wed, 2015-07-15 at 20:32 +0000, Kristen Accardi wrote:
> > 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.

Yes, this is what we are trying to build/automate. Run power-aware
server benchmarks, before and after a kernel patch(es), compare, tell
the delta in a smart and easy to interpret way. Power is measured with
a real power meter. The project is internal so far.


-- 



  
  


Best Regards,

Artem Bityutskiy

  reply	other threads:[~2015-07-17 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 15:37 [Ksummit-discuss] [TECH TOPIC] benchmarking and performance trends 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 [this message]
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=1437161902.14756.15.camel@linux.intel.com \
    --to=artem.bityutskiy@linux.intel.com \
    --cc=clm@fb.com \
    --cc=dwmw2@infradead.org \
    --cc=kaccardi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.