ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Kristen Accardi <kaccardi@gmail.com>
To: Chris Mason <clm@fb.com>, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] benchmarking and performance trends
Date: Wed, 15 Jul 2015 19:23:47 +0000	[thread overview]
Message-ID: <CAH3eK3TtZKdVdFTrQOEPQ0dmXLr-y1w66LW2Qbwwu0VSbiiYiA@mail.gmail.com> (raw)
In-Reply-To: <20150715153725.GA12601@ret.masoncoding.com>

[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]

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.

On Wed, Jul 15, 2015 at 8:37 AM Chris Mason <clm@fb.com> wrote:

> Hi everyone,
>
> I know I never get bored of graphs comparing old/new, but I feel guilty
> suggesting this one yet again.  Still, I think it's important for the
> people trying to push new kernels into production to have a chance to
> talk about the problems we've hit, and/or the changes that have made
> life easier.
>
> We're starting to push 4.0 into prod (122 hosts almost counts), and I'm
> sure we'll backport some wins from 4.2+.  I'm hoping to make this a
> collection point for other benchmarking war stories.  Our biggest gains
> right now are coming from scsi-mq, and early benchmarks show 4.2 has a
> boost that I'm hoping are from the futex locking improvements.
>
> It ties in a little with the new interfaces applications may be able to use
> (restartable sequences etc topic), and I want to ask the broad question of
> "are we doing enough to prevent performance regressions".
>
> We have a long list of people involved on the Facebook side, Jens at the
> very least can talk about the scsi/block-mq benchmarks.  I'd love to hear
> Fengguang's thoughts as well.
>
> -chris
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>

[-- Attachment #2: Type: text/html, Size: 2227 bytes --]

  reply	other threads:[~2015-07-15 19:23 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 [this message]
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
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=CAH3eK3TtZKdVdFTrQOEPQ0dmXLr-y1w66LW2Qbwwu0VSbiiYiA@mail.gmail.com \
    --to=kaccardi@gmail.com \
    --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