Microsoft Word: Typing
Overall Statistics | Microsoft Word: Typing |
---|---|
Elapsed Time | 18:53 |
Read Operations | 5857 |
Write Operations | 2726 |
Data Read | 173.24 MB |
Data Written | 43.30 MB |
Disk Busy Time | 2.63 s |
Average Data Rate | 82.47 MB/s |
It should come as no surprise that there's very little I/O involved in simple tasks like typing. Most of the activity represented in this trace occurs when we open Microsoft Word and save our document. Actually, the latter is far more storage-intensive than you might think. We spent about 18 minutes to transcribe three pages worth of text from a CNN article. The end result was a Word document only 16 KB in size. However, the act of saving actually involves reading more than 100 MB and writing 20 MB.
I/O Trends:
- 85% of all operations occur at a queue depth of one
- 60% of all data transferred is random
- 77% of all operations are random
- 40% of all operations are 32 KB in transfer size
- 24% of all operations are 4 KB in transfer size
- 11% of all operations are 16 KB in transfer size
I suppose I can see some inexpensive reliable SSDs in office machines in the near future, mostly to reduce the failures connected with mechanical drives and speed up boot times and installation times.
SSD not really appropriate.
Unless by office computer you mean where you have the only computer in the office, or files do not need to be shared around the office.
Given the amount of work people do who open large files (where an ssd may be appropriate), they are too small/too expensive to be justified.
Example, large 3d CaD drawings, spend extra money on them loading faster, lose funds for better overall computer (graphics especially).
I find it ironic that the only place your tiny ssd drives are good enough are in computers where speed isn't important in the first place. Until 320GB ssd's can compete with regular magnetic drives, it isn't an option to upgrade.
Imagine the added cost of upgrading the 2442 registered clients to ssd drives! About half could make do with a 120GB drive, and the rest would need at least 160GB and possibly bigger.
That's an expense you can't possibly gain in productivity.
Replacing sas drives with ssd's might make sense for your database or vmware/hyper-v systems, but it isn't going to make much sense on the majority of workstations.