From fda408e0ea652d643ad0005f1863cd560edd942f Mon Sep 17 00:00:00 2001 From: Raghavendra G Date: Wed, 28 May 2014 15:12:42 +0530 Subject: doc: add readdir-ahead documentation Change-Id: Ib6fc3c9b59b498bfe3fb3dfc23dca874bdc0d21d BUG: 1086755 Signed-off-by: Raghavendra G Reviewed-on: http://review.gluster.org/7904 Reviewed-by: Humble Devassy Chirammal Reviewed-by: Niels de Vos Tested-by: Niels de Vos --- doc/features/readdir-ahead.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/features/readdir-ahead.md diff --git a/doc/features/readdir-ahead.md b/doc/features/readdir-ahead.md new file mode 100644 index 00000000000..5302a021202 --- /dev/null +++ b/doc/features/readdir-ahead.md @@ -0,0 +1,14 @@ +## Readdir-ahead ## + +### Summary ### +Provide read-ahead support for directories to improve sequential directory read performance. + +### Owners ### +Brian Foster + +### Detailed Description ### +The read-ahead feature for directories is analogous to read-ahead for files. The objective is to detect sequential directory read operations and establish a pipeline for directory content. When a readdir request is received and fulfilled, preemptively issue subsequent readdir requests to the server in anticipation of those requests from the user. If sequential readdir requests are received, the directory content is already immediately available in the client. If subsequent requests are not sequential or not received, said data is simply dropped and the optimization is bypassed. + +readdir-ahead is currently disabled by default. It can be enabled with the following command: + + gluster volume set readdir-ahead on -- cgit