From: James Page <james.page@ubuntu.com>
To: mnelson@redhat.com, "Blinick,
Stephen L" <stephen.l.blinick@intel.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Memstore performance improvements v0.90 vs v0.87
Date: Thu, 29 Jan 2015 12:51:47 +0000 [thread overview]
Message-ID: <54CA2CE3.8020603@ubuntu.com> (raw)
In-Reply-To: <54C959C4.1010305@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Mark
On 28/01/15 21:51, Mark Nelson wrote:
> Per Sage's suggestion in the perf meeting this morning I dumped
> sysctl -a on both systems and wrote a little script to compare an
> arbitrary number of sysctl output files. It only lists settings
> that have different values and dumps out a csv.
>
> So far it looks like the interesting differences are in:
>
> scheduler numa ipv4 (and ipv6) vm
>
> Script is here:
>
> https://github.com/ceph/ceph-tools/blob/master/cbt/tools/compare_sysctl.py
Useful
>
script - thanks!
I'd like to get the Ubuntu Server and Kernel teams investigating this
disparity as well - would it be possible for you to share the
configurations you are using in detail?
That way I can make sure we are looking at the same thing...
Cheers
James
- --
James Page
Ubuntu and Debian Developer
james.page@ubuntu.com
jamespage@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJUyizjAAoJEL/srsug59jD9NgQAIKfj8w3LMYroO/GlXb3jjnu
6ponX2HTVDNaVqLaYtpevYDUbkgIIEOEcOtxxbORxGnWr7fcXzQtUcp7K0KLtU+r
/SwbEcsBRaS7im1/lqAlXOh67XSSzE0eSpqrWxCPKM6X0kmvD49G0fnTclmax/F6
beUm2Oz9UtRoB28mSIVMcUWbi2vsltbZx4khppu+1WpXqdlHr7fg9lKr2jeSbvXC
23nJ7IEd5zVdxaAxQtjjj9Gjk8TWCFICZIoHwvwOigvCnGihP3Ngnyabx7Gz9sJm
vnyibS+bXHPjIAdUGEtEanOt0lIO8TVbPZM4X3YDaCeEvaoLxqqE832EXShxQ76H
1fDHTu/OQeEyN3udYHit/xgEm3/nMg7Bwb1I4l5TtHgPq8mrXTGqI6zJv9Y1PZ/E
DhmgcTAEPx3/IWBiU1F55Ktgn6N7fIFCrTEDZ6tkuraeG5WJzqf4OEU7XP/8Z1bb
L4VrnBVgNrxDPJOO6u4YNDsacaO4rMCs2U1kQiGKruSXRKnw+RtowoIzIy8O0I6o
lspBJdLjSXXnP/MLVFifFkXyynz/uPIQbg76FA9mVIC3tc7yeXhjB/urrGbbZPuT
IsoVrlsb4IG9Ay4iRCE7yEw9gwqlEhCTtrY9WrhgA/23ihqn1+Hm/4h7ypP+AWmq
XmBsJ1VQyxHnsJgf9R+4
=Zfn0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-01-29 12:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 7:05 Memstore performance improvements v0.90 vs v0.87 Blinick, Stephen L
2015-01-14 22:32 ` Blinick, Stephen L
2015-01-14 22:43 ` Mark Nelson
2015-01-14 23:39 ` Blinick, Stephen L
2015-01-27 21:03 ` Mark Nelson
2015-01-28 1:23 ` Blinick, Stephen L
2015-01-28 21:51 ` Mark Nelson
2015-01-29 12:51 ` James Page [this message]
2015-02-20 9:07 ` James Page
2015-02-20 9:49 ` Blair Bethwaite
2015-02-20 10:09 ` Haomai Wang
2015-02-20 15:38 ` Mark Nelson
[not found] ` <524687337.1545267.1424448115086.JavaMail.zimbra@oxygem.tv>
2015-02-20 16:03 ` Alexandre DERUMIER
2015-02-20 16:12 ` Mark Nelson
[not found] ` <298703592.1573873.1424506210041.JavaMail.zimbra@oxygem.tv>
2015-02-21 8:10 ` Alexandre DERUMIER
[not found] ` <1429598219.1574757.1424509359439.JavaMail.zimbra@oxygem.tv>
2015-02-21 9:02 ` Alexandre DERUMIER
2015-02-20 18:38 ` Stefan Priebe
2015-02-20 15:51 ` Mark Nelson
2015-02-20 15:58 ` James Page
2015-01-14 22:44 ` Somnath Roy
2015-01-14 23:37 ` Blinick, Stephen L
2015-01-15 10:43 ` Andreas Bluemle
2015-01-15 17:09 ` Sage Weil
2015-01-15 17:15 ` Sage Weil
2015-01-19 9:28 ` Andreas Bluemle
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=54CA2CE3.8020603@ubuntu.com \
--to=james.page@ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mnelson@redhat.com \
--cc=stephen.l.blinick@intel.com \
/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.