Skip site navigation (1) Skip section navigation (2)

Re: Effects of setting linux block device readahead size

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: James Mansion <james(at)mansionfamily(dot)plus(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Effects of setting linux block device readahead size
Date: 2008-09-11 05:56:40
Message-ID: Pine.GSO.4.64.0809110150070.3993@westnet.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, 11 Sep 2008, James Mansion wrote:

> Most spinning disks now are nearer to 100MB/s streaming.  You've talked 
> yourself into twice that, random access!

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.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Responses

pgsql-performance by date

Next:From: Peter EisentrautDate: 2008-09-11 09:29:43
Subject: Re: performance impact of non-C locale
Previous:From: Scott MarloweDate: 2008-09-11 05:37:09
Subject: Re: Effects of setting linux block device readahead size

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group