Bug 1689173 - slow 'ls' (crawl/readdir) performance
Summary: slow 'ls' (crawl/readdir) performance
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Xavi Hernandez
QA Contact:
URL:
Whiteboard:
Depends On: 1546649
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-15 10:55 UTC by Nithya Balachandran
Modified: 2020-03-12 14:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: RHGS-Slow-ls
Environment:
Last Closed: 2020-03-12 14:30:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22366 0 None Open cluster/dht: readdirp performance improvements 2020-02-19 06:50:44 UTC
Gluster.org Gerrit 22793 0 None Abandoned slow ls issue 2020-01-13 19:30:27 UTC

Description Nithya Balachandran 2019-03-15 10:55:47 UTC 
+++ This bug was initially created as a clone of Bug #1651048 +++

Description of problem:

When one compares performance of glusterfs's readdir (operations like 'ls', find) with other local filesystems, the performance difference can be very high. Gluster performs slower than other solutions.

Version-Release number of selected component (if applicable):
<ALL>

How reproducible:
Depends on the usecase, where there are lot of files.


Actual results:
Slow 'ls'


Expected results:
Acceptable performance from 'ls'.
Comment 1 Worker Ant 2019-03-15 11:02:48 UTC 
REVIEW: https://review.gluster.org/22366 (cluster/dht: readdirp performance improvements) posted (#1) for review on master by N Balachandran
Comment 2 Worker Ant 2019-05-31 07:09:05 UTC 
REVIEW: https://review.gluster.org/22793 (slow ls issue) posted (#1) for review on master by N Balachandran
Comment 4 Worker Ant 2020-03-12 14:30:09 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/1054, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.