Bug 1458985 - Writing performance difference between to EC volume and 3-way replication volume in windows 7 client
Summary: Writing performance difference between to EC volume and 3-way replication vol...
Keywords:
Status: CLOSED DUPLICATE of bug 1461286
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: disperse
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Ashish Pandey
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-06 02:58 UTC by WenhanShi
Modified: 2020-07-16 09:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-16 04:04:46 UTC
Embargoed:


Attachments (Terms of Use)

Description WenhanShi 2017-06-06 02:58:17 UTC
Description of problem:
From a Windows 7 client, we experienced a huge performance difference between writing to an EC volume and a 3-way replication volume. 

   Windows 7   -> EC(4+2)volume     :22MB/sec
   Windows 7   -> 3-Way replication :90MB/sec

The test method is to copy a 20Gb file to the volume.
And the copy speed is from the copy window in Windows OS.

Version-Release number of selected component (if applicable):
RHGS 3.2

How reproducible:
Every time

Steps to Reproduce:
1. access to an EC volume and a 3-way replicate volume in a windows 7 client
2. copy a big file into EC volume shared directory
3. copy a big file into replicate volume shared directory

Actual results:
Copy to EC volume will cost longer than copy to 3-way replication volume

Expected results:
The copy time should be almost the same.

Additional info:
We also checked this write performance issue from a windows 2012 client, and with no performance difference occurred.

   Windows Server 2012 -> EC(4+2)volume     :100MB/sec
   Windows Server 2012 -> 3-Way replication :100MB/sec

Comment 14 WenhanShi 2017-06-16 04:05:34 UTC

*** This bug has been marked as a duplicate of bug 1461286 ***


Note You need to log in before you can comment on or make changes to this bug.