Description of problem:
Reported for upstream code by Google:
We pulled the latest netkvm changes last week and the performance droped from around 7 Gbps to 2.8. It is a huge drop. Just wanted to let you know.... we will probably revert the February changes if we cant' figure out what is causing this.
On our side, perf was still good at 592fc9e7c428237cebd34baae5231aea5bcc96d8, and it went back on 630ae942aaa7b7a3f3a76bc0a46041f2873e3893. Given the fact that the perf keep normal with vhost+mq on your side, I will also look at our device side which is a virtio-net compatible implementation to cross-check any possible cause. (The perf degradation was measure with exact same device code though).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Could you tell me what is the detail steps and test tool for reproducing this bug? And what is the virtio-win-prewhql version that cause Performance degradation ?
You can use netperf or iperf to test the performance. Run the tools with 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536 packet sizes.
In NetKVM code there is even Tests directory with wrapper for netperf, but you don't have to use it - you can use your own script if it is more convenient.
Builds to compare - latest released driver https://brewweb.devel.redhat.com/buildinfo?buildID=467728 (we still don't have MQ in the release) with
latest virtio-win-prewhql driver.
compared above two versions on comment#3, there is no obvious degradation and increase with multiqueue, is that OK? Or the performance should be increased with multiqueue?
(In reply to wangyu from comment #7)
> Hi Yan,
> compared above two versions on comment#3, there is no obvious degradation
> and increase with multiqueue, is that OK? Or the performance should be
> increased with multiqueue?
With multi-queue when using several streams we should see some performance improvement. With one stream, it should be the same.
change status to "VERIFIED" according to comment#3 and comment#8
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.