Bug 1689173

Summary:	slow 'ls' (crawl/readdir) performance
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	core	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, jahernan, pasik
Target Milestone:	---	Keywords:	Performance, Tracking, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	RHGS-Slow-ls	Environment:
Last Closed:	2020-03-12 14:30:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1546649
Bug Blocks:

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