Bug 763977 (GLUSTER-2245) - cached stat is slower
Summary: cached stat is slower
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-2245
Product: GlusterFS
Classification: Community
Component: nfs
Version: 3.1.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-21 12:45 UTC by Lakshmipathi G
Modified: 2010-12-22 06:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: nfs
Documentation: DNR
CRM:
Verified Versions:


Attachments (Terms of Use)
creat function (200 bytes, text/plain)
2010-12-21 09:45 UTC, Lakshmipathi G
no flags Details
stat (314 bytes, text/plain)
2010-12-21 09:46 UTC, Lakshmipathi G
no flags Details

Description Lakshmipathi G 2010-12-21 09:46:17 UTC
Created attachment 401 [details]
echo where | gdb XF86_S3 core

Comment 1 Lakshmipathi G 2010-12-21 12:45:52 UTC
created a dht  setup with 2 server and nfs mounted on client.
created 1,00,000 empty files and ran attached program,first with dropcaches and 
second time without dropcache. second time the program takes long time to complete than the first.

Comment 2 Shehjar Tikoo 2010-12-22 03:46:27 UTC
Interesting bug report but its not a bug,its a feature.
The 100k file stats perform poorly as compared to 90k files stating because the nfs server's default inode table size is 90k. Once the cold cache stating for 100k files is over, the inode table contains the most recently accessed 90k files, i.e. from file number 10000 to files number 100000.

When the warm cache run  starts, it starts stating from file 1. Because the inode for this is not in the itable, the first 10k files need to be resolved using the expensive fh resolution method, causing the performance drop.

The performance figures were as expected when the tests were run with 90k and less files.


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