Bug 698548

Summary: [virtio-win][performance]virtio-win need optimize write I/O performance.
Product: Red Hat Enterprise Linux 6 Reporter: Quan Wenli <wquan>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: bcao, jasowang, juzhang, michen, mkenneth, qzhang, rhod, tburke, virt-maint, vrozenfe, wquan, xigao
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-01 16:27:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
block-rhel6.1-snp1-windows2k8r2sp1-iometer
none
configuration file for iometer benchmark none

Description Quan Wenli 2011-04-21 08:08:02 UTC 
Created attachment 493731 [details]
block-rhel6.1-snp1-windows2k8r2sp1-iometer

Description of problem:

According to comment #36 in bug 621834,keep tracking virtio-win on wirte i/o 's performance in rhel6.2.

Version-Release number of selected component (if applicable):
Kernel-2.6.32-125.el6.x86_64
qemu-kvm-0.12.1.2-2.152.el6.x86_64
Guest = windows 2k8 r2 sp1
virtio-win-prewhql-0.1-8

How reproducible:

always

Steps to Reproduce:
1.run iometer benmark with attached configuration file.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Quan Wenli 2011-04-21 08:09:27 UTC 
Created attachment 493732 [details]
configuration file for iometer benchmark
Comment 3 Vadim Rozenfeld 2011-12-09 11:39:13 UTC 
Moving this bug to rhel-6.4.0.
I don't believe we will have enough time
to do some serious optimization in rhel-6.3.0
time frame.
Comment 10 Vadim Rozenfeld 2013-09-08 06:00:05 UTC 
please re-check with build 69 available at https://brewweb.devel.redhat.com/buildinfo?buildID=293655
I would like to close this bug if the results are the same as shown in comment #9, because we will not get better performance in 6.5 

Thanks
Vadim.
Comment 13 Xiaomei Gao 2013-10-28 03:37:05 UTC 
Hi, Vadim

    Could we set the bug to verified status and open new bug in 6.6 to track the issue described in comment #11, or what better suggestions to handle the bug?

Thanks
Xiaomei
Comment 14 Vadim Rozenfeld 2013-10-28 07:01:29 UTC 
(In reply to Xiaomei Gao from comment #13)
> Hi, Vadim
> 
>     Could we set the bug to verified status and open new bug in 6.6 to track
> the issue described in comment #11,

Hi Xiaomei,
Yes, it will be perfect.
Best regards,
Vadim.

> or what better suggestions to handle the
> bug?
> 
> Thanks
> Xiaomei
Comment 15 Xiaomei Gao 2013-10-28 10:46:20 UTC 
Close the bug to verified status and open Bug 1023894 in 6.6 to track the first issue described in comment #11.