Robustness testing
From Linux NFS
(Difference between revisions)
(→NFSv4 Robustness testing) |
|||
| Line 2: | Line 2: | ||
There are 3 tools used to test NFSv4 robustness. This tools are used to tests core filesystems functions : read/write/create ... in various configurations. | There are 3 tools used to test NFSv4 robustness. This tools are used to tests core filesystems functions : read/write/create ... in various configurations. | ||
| - | * [[#Fsstress]] : random sequence of FS operations performed by concurent processes. | + | * [[#Fsstress|fsstress]] : random sequence of FS operations performed by concurent processes. |
| - | * [[#Fsx]] | + | * [[#Fsx|fsx]] |
| - | * [[#FFSB]] | + | * [[#FFSB|ffsb]] |
Each time a NFSv4 is able to complete one test sequence, this test should be conserved for non regression testing. | Each time a NFSv4 is able to complete one test sequence, this test should be conserved for non regression testing. | ||
Revision as of 10:24, 18 May 2005
NFSv4 Robustness testing
There are 3 tools used to test NFSv4 robustness. This tools are used to tests core filesystems functions : read/write/create ... in various configurations.
Each time a NFSv4 is able to complete one test sequence, this test should be conserved for non regression testing.
Links
List of tests tools that should be usefull to test NFSv4.
Main results
Last kernel tested is Linux 2.6.12-rc3 more patches CITI_NFS4_ALL-4.
NFS v4 is able to complete this testes:
- fsx
- fsstress running 5 days in this configuration
- 10 threads
- 100 operation list lenght
- FFSB running 5hours with this profile:
- num_files=1200000
- num_dirs=100
- max_filesize=4096
- min_filesize=4096
- num_threads=10
- read_weight=3
- write_weight=1
- append_weight=1
- write_random=1
- write_size=4096
- write_blocksize=4096
- read_size=4096
- read_blocksize=4096
