Test
A simple test tool was written to test the maximal number of files NFSv4 is able to manage. It create a directory. In this directory the test create 100 files, and measure the time it needs to stat the directory. While it does not fail, it continue adding 100 files and measuring the stat time (readdir, in python). Evolution of the time of stat is displayed below
Conclusion
The test has been blocked after having measured the time to stat 15,699 files. At this point I note :
- On the server, files 15700 to 15799 are created
- test script is blocked
- stat is not returning, nor in the python script, nor with the command line (ls)
At this point NFSv4 is not able to manage more than 15699. (Perhaps a little more, because the step of the test is 100, and so the real limit is between 15699 and 15799). That is not enought.
Software configuration
- Server :
- Export options are :
/export *(rw,wdelay,insecure,no_root_squash,no_subtree_check,fsid=0)
- mount options, NFSv4 :
rsize=32768,wsize=32768,timeo=14,intr,noauto
- Linux 2.6.12-rc4-CITI_NFS4_ALL-1
hardware configuration
(Client and Server)
- 2 processors : Intel(R)
- Xeon(TM) CPU 2.80GHz, cache 512 KB
- Total memory: 2Gb
- Ethernet: 1Gb/s link
- Distribution : modified Fedora Core 2
