Re: Effects of setting linux block device readahead size

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greg Smith wrote:
The point I was trying to make there is that even under impossibly optimal circumstances, you'd be hard pressed to blow out the disk's read cache with seek-dominated data even if you read a lot at each seek point. That idea didn't make it from my head into writing very well though.

Isn't there a bigger danger in blowing out the cache on the controller and causing premature pageout of its dirty pages?

If you could get the readahead to work on the drive and not return data to the controller, that might be dandy, but I'm sceptical.

James



[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux