Test
Yet another stress test :)
A simple test tool was written to test the maximal NFSv4 mount alowed and the maximum NFSv4 export a server can perform. It create, export a directory on a server and mount it on the client, until the test fail
Conclusion
The test was ran 3 days. The server reaches 13.000 directories exported. Whithin this conditions (13000 directories exported)
- exportfs process is using 100% CPU
- exportfs operation takes more than 1m 10s
- unexporting operation mey cause some problems : exportfs: failed to lock /var/lib/nfs/etab
for 1024 directories, time of export and mount is less than 1 second. rpc.mountd and exportfs uses less than 15% CPU
for 3000 directories, time of export and mount is 6 seconds. rpc.mountd and exportfs uses 40% and 15% CPU
for 13000 directories, time of export and mount is more than 1minute 10s. exportfs uses 100% CPU
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 -osec=krb5
- Linux 2.6.12-rc4-CITI_NFS4_ALL-1
hardware configuration
Client
- 2 processors : Intel(R)
- Xeon(TM) CPU 2.80GHz, cache 512 KB
- Total memory: 2Gb
- Ethernet: 1Gb/s link
- Distribution : modified Fedora Core 2
Server
- 4 processors : Intel(R) Xeon(TM) CPU 2.80GHz, cache 512 KB
- Total memory: 24Gb
- Ethernet: 1Gb/s link
- Distribution : modified Fedora Core 2
