| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Subject: | Re: Optimize kernel readahead using buffer access strategy |
| Date: | 2014-01-14 14:35:07 |
| Message-ID: | CAGTBQpb6ZxHyC0v6AfHyyv=erC4rsyDbp6u7EZoYLt1eAeF-hA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 14, 2014 at 8:58 AM, KONDO Mitsumasa
<kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>
> In my past patch, it is significant bug which is mistaken caluculation of
> offset in posix_fadvise():-( However it works well without problem in
> pgbench.
> Because pgbench transactions are always random access...
Did you notice any difference?
AFAIK, when specifying read patterns (ie, RANDOM, SEQUENTIAL and stuff
like that), the offset doesn't matter. At least in linux.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2014-01-14 14:39:57 | Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance |
| Previous Message | Claudio Freire | 2014-01-14 14:34:32 | Re: Optimize kernel readahead using buffer access strategy |