Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-96854

Performance Degradation(aio=threads) between Upstream Commit b75c5f9 and 984a32f

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • qemu-kvm-10.0.0-8.el10
    • No
    • Important
    • 1
    • rhel-virt-storage
    • 24
    • 0
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Planning backlog
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      Performance Degradation(aio=threads) between Upstream Commit b75c5f9 and 984a32f

      Please provide the package NVR for which the bug is seen:

      Upstream commit 984a32f in rhel10.1 host

      How reproducible is this bug?:

      100%

      Steps to reproduce

      Building the upstream qemu code based on commit 984a32f and b75c5f9, and start the performance compare with aio=threads for the testing disk.

      For upstream qemu code build:

      # ./configure --target-list=x86_64-softmmu --enable-debug --enable-kvm --enable-seccomp --enable-slirp --enable-vnc --enable-linux-io-uring --enable-linux-aio && make && make install 

      And for guest setup and fio testing, please refer to https://issues.redhat.com/browse/RHEL-66064?focusedId=27232751&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27232751

       

      Expected results

      No performance regression

      Actual results

      Performance regression for both nvme block disk and file.

              kwolf@redhat.com Kevin Wolf
              timao@redhat.com Tingting Mao
              virt-maint virt-maint
              Tingting Mao Tingting Mao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: