Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1628965

Summary: Performance Degradation running PVP on all packet sizes. rfc 2544 Throughput tests
Product: Red Hat Enterprise Linux 7 Reporter: Bob Fubel <bfubel>
Component: qemu-kvm-rhevAssignee: Maxime Coquelin <maxime.coquelin>
Status: CLOSED NOTABUG QA Contact: Pei Zhang <pezhang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: ailan, atragler, chayang, ctrautma, juzhang, maxime.coquelin, michen, pezhang, siliu, tli, virt-maint
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-18 14:14:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xena Test File none

Description Bob Fubel 2018-09-14 14:16:11 UTC
Description of problem:
Performance has dropped between QEMU 2.10 and 2.12. Running in ixgbe.
Running in RHEL7.5 and changing QEMU from 2.10 to 2.12 I am seeing preformace degradation.  

I am closing the original BUG 1616306 https://bugzilla.redhat.com/show_bug.cgi?id=1616306
and opeing this one to track this as a QEMU problem.


Version-Release number of selected component (if applicable):
RHEL 7.5
3.10.0-862.el7.x86_64

qemu-kvm-common-rhev-2.12.0-12.el7.x86_64
ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch
qemu-img-rhev-2.12.0-12.el7.x86_64
qemu-kvm-rhev-2.12.0-12.el7.x86_64
qemu-kvm-rhev-debuginfo-2.12.0-12.el7.x86_64
qemu-kvm-tools-rhev-2.12.0-12.el7.x86_64


How reproducible:
attached log for host and guests. running xena traffic generator. RFC2544 throughtput test 0% loss test.
some loss seen for 60 second trials and large loss seen on 20 minute trials.



Actual results:
Attached Results:


Expected results:
Perfoamce should not have changed.

Additional info:
Using CPU-Partioning tunded-adm profile on host and guest.


I have also modified the vcpu pinning as requmened by Maxime Coquelin,

Comment 2 Bob Fubel 2018-09-14 14:26:51 UTC
Created attachment 1483343 [details]
Xena Test File

Comment 4 Pei Zhang 2018-09-17 03:13:36 UTC
I and Ting are debugging this lower throughput issue, we found probably the vCPU ping cause it. As the interface of qemu 'info cpus' changes a bit like below, this may affect the automation script to set vCPU ping. 

With qemu 2.10:
(qemu) info cpus
* CPU #0: pc=0x0000000007f06173 (halted) thread_id=11945
  CPU #1: pc=0x00000000000fd0f5 (halted) thread_id=11946
  CPU #2: pc=0x00000000000fd0f5 (halted) thread_id=11947


With qemu 2.12:
(qemu) info cpus
* CPU #0: thread_id=22877
  CPU #1: thread_id=22878
  CPU #2: thread_id=22879
  CPU #3: thread_id=22880
  CPU #4: thread_id=22881


By the way, we don't hit this throughput issue, it always works as expected with both qemu2.10 and qemu2.12. We are testing from libvirt layer, that's why we don't affected by above "info cpus" changes. Besides, the emulator CPUs don't share same host CPUs with vCPUs. Below is the libvirt CPU configuration which we use.

  <vcpu placement='static'>6</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='30'/>
    <vcpupin vcpu='1' cpuset='31'/>
    <vcpupin vcpu='2' cpuset='29'/>
    <vcpupin vcpu='3' cpuset='27'/>
    <vcpupin vcpu='4' cpuset='25'/>
    <vcpupin vcpu='5' cpuset='23'/>
    <emulatorpin cpuset='18,20,22,24,26,28'/>
  </cputune>

Comment 5 Eelco Chaudron 2018-09-17 06:40:07 UTC
*** Bug 1616306 has been marked as a duplicate of this bug. ***

Comment 6 Maxime Coquelin 2018-09-17 14:34:59 UTC
Hi Pei,

In your setup, are you trying QEMU 2.12 on RHEL 7.5 or RHEL 7.6?

Comment 7 Bob Fubel 2018-09-17 16:32:49 UTC
Li Ting is testing tonight to confim the new way of pinning the CPU's
will work for all the longer tests. if it does then we will be able to close off this bug.  And document the change in the way the pinning is working.

Bob

<vcpu placement='static'>6</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='30'/>
    <vcpupin vcpu='1' cpuset='31'/>
    <vcpupin vcpu='2' cpuset='29'/>
    <vcpupin vcpu='3' cpuset='27'/>
    <vcpupin vcpu='4' cpuset='25'/>
    <vcpupin vcpu='5' cpuset='23'/>
    <emulatorpin cpuset='18,20,22,24,26,28'/>
  </cputune>




On 09/15/2018 10:13 AM, Amnon Ilan wrote:
> Hi Chris, Bob, 
>
> Please note that you cannot change the qemu version without the RHEL version.
> RHEL7.6 goes with qemu-2.12
> RHEL7.5 goes with qemu-2.10
>
> That's the way virt-qe are testing it, so if you want to switch to qemu-2.12 you should 
> also switch to RHEL7.6.
>
> From the new BZ is seems that you are trying an untested combination: 7.5+qemu-2.12
>
> Thanks,
> Amnon
>
>
>
> On Fri, Sep 14, 2018 at 7:57 PM Christian Trautman <ctrautma> wrote:
>
>     Just to clarify, the performance issue is only when updating to qemu 2.12.
>
>     All tests with 7.5 with qemu 2.10 have not had a problem with either ovs 2.9 or ovs 2.10.
>
>     We closed the previous bug and opened a new one to get the information precise and easier to follow.
>
>     https://bugzilla.redhat.com/show_bug.cgi?id=1628965
>
>     -Christian,

Comment 8 Pei Zhang 2018-09-18 05:13:23 UTC
(In reply to Maxime Coquelin from comment #6)
> Hi Pei,
> 
> In your setup, are you trying QEMU 2.12 on RHEL 7.5 or RHEL 7.6?

Hi Maxime,

I'm testing QEMU 2.12 on RHEL7.6.


Best regards,
Pei

Comment 9 Amnon Ilan 2018-09-18 10:41:40 UTC
(In reply to Bob Fubel from comment #7)
> Li Ting is testing tonight to confim the new way of pinning the CPU's
> will work for all the longer tests. if it does then we will be able to close
> off this bug.  And document the change in the way the pinning is working.
> 
> Bob
> 
> <vcpu placement='static'>6</vcpu>
>   <cputune>
>     <vcpupin vcpu='0' cpuset='30'/>
>     <vcpupin vcpu='1' cpuset='31'/>
>     <vcpupin vcpu='2' cpuset='29'/>
>     <vcpupin vcpu='3' cpuset='27'/>
>     <vcpupin vcpu='4' cpuset='25'/>
>     <vcpupin vcpu='5' cpuset='23'/>
>     <emulatorpin cpuset='18,20,22,24,26,28'/>
>   </cputune>
> 

Li Ting, what were the results of your test?
(and was it with 7.6?)

Thanks!
Amnon

Comment 10 Bob Fubel 2018-09-18 14:14:45 UTC
Testing looked good. and I am closing this bug. The QEMU 2.12 and RHEL 7.6 requiement should be documented. 

 

On 09/18/2018 03:47 AM, Ting Li wrote:
> Hi Chris,
>
> I have finished to run a gating CI with qemu2.12 on dell50 i40e nic after modified the vsperf qemu.py, the performance are stable now. Following is the job and result link, please have a look.
> job link:
> https://beaker.engineering.redhat.com/jobs/2772869
> result link:
> https://docs.google.com/spreadsheets/d/1-ZyB6vpCtOwPsXbHjPPn2uFaTSwXZS01mn0CJOtzTZo/edit#gid=1891949767
>
> thanks,
> Li Ting
>

Comment 11 Red Hat Bugzilla 2023-09-14 04:38:20 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days