Nick Holland wrote: > however, maybe locate.updatedb could be adjusted to put an optional > delay between disk queries...
What would be the relevant metric, how close to capacity a drive is working at? On a one-user system, it could be feasible to wait until usage is zero or close to it. On a multi-user system or working server that won't happen. iostat tells KB/transfer, transfers/second, and MB/second for any given disk. However, it doesn't say how the measured values relate to the maximum possible for that particular drive. For example, testing four different drives I have: A SSD shows a max between 13 and 17 MB/s async and between 0.36 and 0.73 sync. A CF shows just over 8 MB/s async and a bit less than 4 MB/s sync A 2.5" hd shows 15 - 20 MB/s async and 16-17 sync A usb hd shows around a little over 6 MB/s async and a little less over 6 MB/s sync /Lars
