From: Chris Mason <clm@fb.com>
To: <ksummit-discuss@lists.linuxfoundation.org>
Subject: [Ksummit-discuss] [TECH TOPIC] benchmarking and performance trends
Date: Wed, 15 Jul 2015 11:37:25 -0400 [thread overview]
Message-ID: <20150715153725.GA12601@ret.masoncoding.com> (raw)
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
next reply other threads:[~2015-07-15 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 15:37 Chris Mason [this message]
2015-07-15 19:23 ` [Ksummit-discuss] [TECH TOPIC] benchmarking and performance trends 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
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=20150715153725.GA12601@ret.masoncoding.com \
--to=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 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.