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
