From: Aaron Lu <aaron.lu@intel.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: kernel test robot <xiaolong.ye@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org, "David S. Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [sctp] a6c2f79287: netperf.Throughput_Mbps -37.2% regression
Date: Wed, 17 Aug 2016 17:20:01 +0800 [thread overview]
Message-ID: <80bbef60-34ed-0bf1-f1c5-8285b713c2f7@intel.com> (raw)
In-Reply-To: <CADvbK_dqSTArYJQGD9--vi4vyV-kfAg50=cK4oc7AhGzSwbLXQ@mail.gmail.com>
On 08/17/2016 04:58 PM, Xin Long wrote:
>>
>> It doesn't change on my desktop Sandybridge.
>>
>> $ cat 4.7.0-rc6-01199-g116558d316e8/0/netperf.json
>> {
>> "netperf.Throughput_Mbps": [
>> 748.2056249999998
>> ]
>> }
>>
>> Where commit 116558d316e8 is based on top of the last test commit
>> 98dd2532b14e with the sent_count removed.
> Nice job
> I guess it may be because of your system memory limitation
>
> sctp_chunk size is bigger than before, netpref produced a lot
> of sctp_chunk in send queue.
>
> can you check the memory of your systems when the test is
> running, to see if memory is the bottle neck of this test ?
We have a monitor to dump /proc/meminfo every second during the run.
On my desktop, the result is -
At start:
time: 1471413103.386122645
MemTotal: 14193468 kB
MemFree: 13849136 kB
MemAvailable: 13789204 kB
In the middle of the run:
time: 1471413254.363430637
MemTotal: 14193468 kB
MemFree: 13811732 kB
MemAvailable: 13756376 kB
When the test is about to finish:
time: 1471413391.294215121
MemTotal: 14193468 kB
MemFree: 13286080 kB
MemAvailable: 13749416 kB
It doesn't seem memory is an issue.
The whole dump is about the same.
The MemFree and MemAvailable doesn't change much.
Thanks,
Aaron
next prev parent reply other threads:[~2016-08-17 9:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 1:54 kernel test robot
2016-07-28 7:01 ` Xin Long
2016-08-05 3:31 ` [LKP] " Aaron Lu
2016-08-05 11:53 ` Xin Long
2016-08-08 2:10 ` Aaron Lu
2016-08-16 2:38 ` Aaron Lu
2016-08-16 8:02 ` Xin Long
2016-08-16 8:30 ` Aaron Lu
2016-08-16 8:51 ` Aaron Lu
2016-08-16 9:56 ` Xin Long
2016-08-17 5:04 ` Aaron Lu
2016-08-17 5:34 ` Xin Long
2016-08-17 5:34 ` Aaron Lu
2016-08-17 5:41 ` Xin Long
2016-08-17 6:14 ` Aaron Lu
2016-08-17 6:37 ` Aaron Lu
2016-08-17 6:42 ` Aaron Lu
2016-08-17 7:35 ` Xin Long
2016-08-17 7:42 ` Aaron Lu
2016-08-17 7:53 ` Aaron Lu
2016-08-17 8:02 ` Xin Long
2016-08-17 8:48 ` Aaron Lu
2016-08-17 8:58 ` Xin Long
2016-08-17 9:20 ` Aaron Lu [this message]
2016-08-17 18:06 ` Xin Long
2016-08-18 3:21 ` Aaron Lu
2016-08-18 12:45 ` Xin Long
2016-08-19 5:29 ` Aaron Lu
2016-08-19 7:19 ` Marcelo Ricardo Leitner
2016-08-19 7:24 ` Aaron Lu
2016-08-22 21:44 ` Marcelo Ricardo Leitner
2016-08-23 9:19 ` Aaron Lu
2016-09-30 7:05 ` Aaron Lu
2016-10-03 2:32 ` Xin Long
2016-10-09 7:41 ` Aaron Lu
2016-08-16 18:34 ` Xin Long
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=80bbef60-34ed-0bf1-f1c5-8285b713c2f7@intel.com \
--to=aaron.lu@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=lucien.xin@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@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 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®