Re: Effects of setting linux block device readahead size - Mailing list pgsql-performance

From Matthew Wakeling
Subject Re: Effects of setting linux block device readahead size
Date
Msg-id alpine.DEB.1.10.0809151717001.23198@aragorn.flymine.org
Whole thread Raw
In response to Re: Effects of setting linux block device readahead size  ("Scott Carey" <scott@richrelevance.com>)
Responses Re: Effects of setting linux block device readahead size  ("Scott Carey" <scott@richrelevance.com>)
List pgsql-performance
On Thu, 11 Sep 2008, Scott Carey wrote:
> Preliminary summary:
>
> readahead  |  8 conc read rate  |  1 conc read rate
> 49152  |  311  |  314
> 16384  |  312  |  312
> 12288  |  304  |  309
>  8192  |  292  |
>  4096  |  264  |
>  2048  |  211  |
>  1024  |  162  |  302
>   512  |  108  |
>   256  |  81  | 300
>     8  |  38  |

What io scheduler are you using? The anticipatory scheduler is meant to
prevent this slowdown with multiple concurrent reads.

Matthew


--
And the lexer will say "Oh look, there's a null string. Oooh, there's
another. And another.", and will fall over spectacularly when it realises
there are actually rather a lot.
         - Computer Science Lecturer (edited)

pgsql-performance by date:

Previous
From: Craig James
Date:
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Next
From: "Scott Carey"
Date:
Subject: Re: Effects of setting linux block device readahead size