Test Cases for the File System Performance Test (Windows Embedded CE 6.0)
1/6/2010
The following table shows the test cases for the File System Performance Test.
| Test case | Description |
|---|---|
1001 |
Measures the I/O throughput of writing a 2MB file in data blocks of 512 bytes using the WriteFile function. The test fails if the file cannot be created, or if any of the writes fail. |
1002 |
Measures the I/O throughput of reading a 2MB file in data blocks of 512 bytes using the ReadFile function. The test fails if the file cannot be created, or if any of the reads fail. |
1003 |
Measures the I/O throughput of writing out 2MB of data by performing random seeks followed by 512 byte writes using the SetFilePointer and WriteFile functions. The test fails if the file cannot be created, or if any of the seeks or writes fail. |
1004 |
Measures the I/O throughput of reading in 2MB of data by performing random seeks followed by 512 byte reads using the SetFilePointer and ReadFile functions. The test fails if the file cannot be created, or if any seeks or reads fail. |
1005 |
Measure the I/O throughput of reading in a 2MB file backwards in data blocks of 512 bytes using the SetFilePointer and ReadFile functions. The test fails if the file cannot be created, or if any reads fail. |
2001 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 128 bytes. The overall test fails if any of the individual tests fail. |
2002 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 256 bytes. The overall test fails if any of the individual tests fail. |
2003 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 512 bytes. The overall test fails if any of the individual tests fail. |
2004 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 1024 bytes. The overall test fails if any of the individual tests fail. |
2005 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 2048 bytes. The overall test fails if any of the individual tests fail. |
2006 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 4096 bytes. The overall test fails if any of the individual tests fail. |
2007 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 8192 bytes. The overall test fails if any of the individual tests fail. |
2008 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 16384 bytes. The overall test fails if any of the individual tests fail. |
2009 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 32768 bytes. The overall test fails if any of the individual tests fail. |
2010 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 65536 bytes. The overall test fails if any of the individual tests fail. |
2011 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 131072 bytes. The overall test fails if any of the individual tests fail. |
2012 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 262144 bytes. The overall test fails if any of the individual tests fail. |
2013 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 524288 bytes. The overall test fails if any of the individual tests fail. |
2014 |
Run all the performance tests defined by test cases 1001 to 1005 with data blocks of 1048576 bytes. The overall test fails if any of the individual tests fail. |
3001 |
Measures the speed of creating a deep nested directory tree 10 levels deep using the CreateDirectory function. The test fails if any of the directories cannot be created. |
3002 |
Measures the speed of creating a deep nested directory tree 15 levels deep using the CreateDirectory function. The test fails if any of the directories cannot be created. |
3003 |
Measures the speed of creating a deep nested directory tree 20 levels deep using the CreateDirectory function. The test fails if any of the directories cannot be created. |
3004 |
Measures the speed of creating a 500MB file by using SetFilePointer and SetEndOfFile functions. The test fails if the file cannot be created, or if either of the operations fail. |
3005 |
Measures the seek speed by performing 1000 random seeks followed by 1 byte reads using the SetFilePointer and ReadFile functions. The test fails if the file cannot be created, or if any of the seeks or reads fail. |
3006 |
Measures the seek speed by performing 1000 random seeks followed by 1 byte writes using the SetFilePointer and WriteFile functions. The test fails if the file cannot be created, or if any of the seeks or writes fail. |
4001 |
Measures the I/O throughput by continuously reading and appending data to a 100MB file using the SetFilePointer, ReadFile, and WriteFile functions. This test is intended to simulate the behavior of a Digital Video Recorder (DVR) device, which often records and plays back data from the same file. The test fails if the file cannot be created, or if any of the seeks, reads, or writes fail. If the storage device has insufficient space (~300MB), the test will skip. |
4002 |
Measures the speed of copying a folder with 100 files from the storage device to the root directory of the device using the FindFirstFile, FindNextFile, and CopyFile functions. The test fails if the directory or files cannot be created, or if the copy process fails. If this test is run on the Object Store rather than a storage device, then the files will be both created and copied on the Object Store. |
4003 |
Measures the speed of copying a folder with 100 files from the root directory to a storage device using the FindFirstFile, FindNextFile, and CopyFile functions. The test fails if the directory or files cannot be created, or if the copy process fails. If this test is run on the Object Store rather than a storage device, then the files will be both created and copied on the Object Store. |