Bug 1322624 - Disk usage command du with -s option, reporting sum of usage in current directory, too slow, does not scale (43+ min) on glusterfs
Summary: Disk usage command du with -s option, reporting sum of usage in current direc...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: core
Version: rhgs-3.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Pranith Kumar K
QA Contact: Ambarish
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 22:33 UTC by Diane Feddema
Modified: 2018-02-07 05:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-07 05:48:31 UTC
Target Upstream Version:
asoman: needinfo+

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Diane Feddema 2016-03-30 22:33:52 UTC 
Description of problem:
Disk usage command, "du -sh /glusterfs/users/dfeddema/perf10" 40 times slower
with glusterfs than XFS filesystem for same directory contents.

$ time du -sh /glusterfs/users/dfeddema/perf10
96G    /glusterfs/users/dfeddema/perf10

real    43m24.491s
user    0m13.700s
sys    1m16.336s

Version-Release number of selected component (if applicable):
$ glusterfs --version
glusterfs 3.6.2 built on Jan 22 2015 12:59:55



How reproducible:  100%


Steps to Reproduce:
1. install glusterfs 3.6.2
2. create 90+ GB directory with 128 sub-directories and 4949914 files.
3. run "du -sh glusterfs_directory"

Actual results:


Expected results:


Additional info:
Comment 8 Amar Tumballi 2018-02-07 05:48:31 UTC 
Thank you for your bug report.

We are no longer releasing any bug fixes or, any other updates for this version. But this particular performance issue of readdir has been improved in the higher versions. This bug will be set to CLOSED WORKSFORME to reflect this. Please reopen if the problem continues to be observed after upgrading to a latest version.
Note You need to log in before you can comment on or make changes to this bug.