From: Dave Hansen <dave.hansen@intel.com>
To: Jet Chen <jet.chen@intel.com>, Miklos Szeredi <mszeredi@suse.cz>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [vfs] 662aa027bda: -7.2% will-it-scale.scalability
Date: Tue, 27 May 2014 11:19:40 -0700 [thread overview]
Message-ID: <5384D73C.2030109@intel.com> (raw)
In-Reply-To: <5384B634.7080902@intel.com>
On 05/27/2014 08:58 AM, Jet Chen wrote:
> 9f498c77b4332b4 662aa027bdaa082aa3dd21886
> --------------- -------------------------
> 0.63 ~ 0% -7.2% 0.58 ~ 0% TOTAL will-it-scale.scalability
> 12861563 ~ 0% -1.1% 12715565 ~ 0% TOTAL will-it-scale.per_process_ops
There's something funky here.
What are the numbers being factored in to 'will-it-scale.scalability'
and 'will-it-scale.per_process_ops'? Could you share the raw csv's that
will-it-scale generated?
Since 'per_process_ops' is only off by 1.1%, my suspicion is that some
consistent skew on the 1-process case is getting magnified in to the
scalability number.
prev parent reply other threads:[~2014-05-27 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 15:58 Jet Chen
2014-05-27 16:25 ` Miklos Szeredi
2014-05-27 18:19 ` Dave Hansen [this message]
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=5384D73C.2030109@intel.com \
--to=dave.hansen@intel.com \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mszeredi@suse.cz \
/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
all inboxes | Powered by JetHome®