From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [net] ceb5d58b21: -69.2% fsmark.files_per_sec
Date: Mon, 28 Dec 2015 08:58:17 +0800 [thread overview]
Message-ID: <8760zj8k46.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <CANn89iJxF_qJwk0AmFVd57oexPzeB596KRL0r1HehP23JQM-dw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
Eric Dumazet <edumazet@google.com> writes:
> On Wed, Dec 23, 2015 at 9:49 PM, kernel test robot
> <ying.huang@linux.intel.com> wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> commit ceb5d58b217098a657f3850b7a2640f995032e62 ("net: fix sock_wake_async() rcu protection")
>>
>>
>> =========================================================================================
>> compiler/cpufreq_governor/disk/filesize/fs2/fs/iterations/kconfig/nr_threads/rootfs/sync_method/tbox_group/test_size/testcase:
>> gcc-4.9/performance/1BRD_48G/4M/nfsv4/xfs/1x/x86_64-rhel/64t/debian-x86_64-2015-02-07.cgz/NoSync/lkp-hsx04/40G/fsmark
>>
>> commit:
>> 9cd3e072b0be17446e37d7414eac8a3499e0601e
>> ceb5d58b217098a657f3850b7a2640f995032e62
>>
>> 9cd3e072b0be1744 ceb5d58b217098a657f3850b7a
>> ---------------- --------------------------
>> %stddev %change %stddev
>
>> Thanks,
>> Ying Huang
>
> Hi Ying. I have no idea what these confusing numbers mean.
>
> Is your benchmark running faster (good thing) or slower (sorry, but we
> fixed a bug)
The benchmark running slower now. This has big impact on performance,
maybe we can find some clue to optimize from the test result? The
benchmark is about file IO performance on a loop back mounted NFS.
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [LKP] [net] ceb5d58b21: -69.2% fsmark.files_per_sec
Date: Mon, 28 Dec 2015 08:58:17 +0800 [thread overview]
Message-ID: <8760zj8k46.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <CANn89iJxF_qJwk0AmFVd57oexPzeB596KRL0r1HehP23JQM-dw@mail.gmail.com> (Eric Dumazet's message of "Thu, 24 Dec 2015 05:17:08 -0800")
Eric Dumazet <edumazet@google.com> writes:
> On Wed, Dec 23, 2015 at 9:49 PM, kernel test robot
> <ying.huang@linux.intel.com> wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> commit ceb5d58b217098a657f3850b7a2640f995032e62 ("net: fix sock_wake_async() rcu protection")
>>
>>
>> =========================================================================================
>> compiler/cpufreq_governor/disk/filesize/fs2/fs/iterations/kconfig/nr_threads/rootfs/sync_method/tbox_group/test_size/testcase:
>> gcc-4.9/performance/1BRD_48G/4M/nfsv4/xfs/1x/x86_64-rhel/64t/debian-x86_64-2015-02-07.cgz/NoSync/lkp-hsx04/40G/fsmark
>>
>> commit:
>> 9cd3e072b0be17446e37d7414eac8a3499e0601e
>> ceb5d58b217098a657f3850b7a2640f995032e62
>>
>> 9cd3e072b0be1744 ceb5d58b217098a657f3850b7a
>> ---------------- --------------------------
>> %stddev %change %stddev
>
>> Thanks,
>> Ying Huang
>
> Hi Ying. I have no idea what these confusing numbers mean.
>
> Is your benchmark running faster (good thing) or slower (sorry, but we
> fixed a bug)
The benchmark running slower now. This has big impact on performance,
maybe we can find some clue to optimize from the test result? The
benchmark is about file IO performance on a loop back mounted NFS.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2015-12-28 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 5:49 [net] ceb5d58b21: -69.2% fsmark.files_per_sec kernel test robot
2015-12-24 13:17 ` Eric Dumazet
2015-12-24 13:17 ` Eric Dumazet
2015-12-28 0:58 ` Huang, Ying [this message]
2015-12-28 0:58 ` [LKP] " Huang, Ying
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=8760zj8k46.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.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.