-
Notifications
You must be signed in to change notification settings - Fork 4
Performance
TechieGuy12 edited this page Aug 5, 2022
·
5 revisions
The performance of File Verification will depend on many factors - hard drive speed, processor, speed of the hard drive connection, size of files, etc. Each machine will see different performance from File Verification.
If you are looking for a clue as to the performance of File Verificaiton, I will share some of the performance numbers from the system I use for storing my files.
The specs for my system are as follows:
- Processor: i5-3470 @ 3.20 GHz
- Memory: 12 GB
- Operating System: Windows 10 Pro
- Hard Drives: 2 x 8 TB WD Gold
The hard drives are in a DAS (direct attached storage) unit connected via USB 3.0. They are pooled (mirrored) using DrivePool.
Each month I run File Verification against the files to ensure they have not been changed. The results below are from the monthly run:
| Size (bytes) | Files | Avg. File Size | Time (seconds) | Avg. Read Speed (bytes) |
|---|---|---|---|---|
| 102,738,620,416 | 9,939 | 10,336,917 | 570 | 180,294,435 |
| 10,177,970,176 | 3,169 | 3,211,729 | 59 | 171,785,886 |
| 6,526,386,176 | 2,628 | 2,483,404 | 38 | 173,168,812 |
In the above table, File Verification is run using 12 threads.