Comment 8 for bug 492841
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
For the third part, the throughput is about as high as your disk is capable of given the spread of files. The reason it's not max'd out is that we have to seek over bits of the disk we don't want/need in the page cache. We use the I/O elevator as efficiently as we can to merge reads, but at the end of the day, we have to seek.
Even more interesting is that the obvious "dips" correspond to the on-disk positions of your inode tables and suchlike ;) they take quite a jump to get over