From: Andres Freund <andres@2ndquadrant.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: pgsql-performance@postgresql.org, Maxim Boguk <maxim.boguk@gmail.com>
Cc: David Kerr <dmk@mr-paradox.net>
Subject: Re: Massive I/O spikes during checkpoint
Date: Tue, 10 Jul 2012 15:41:18 +0200
Message-ID: <201207101541.18492.andres@2ndquadrant.com> (raw)
In-Reply-To: <CAMkU=1zq2DDFnnoqK_TnFgzz7WF5SSTjvAVU7ga2Ljbpu_yECQ@mail.gmail.com>
References: <27C32FD4-0142-44FE-8488-9F366DC75966@mr-paradox.net>
<201207101444.14887.andres@2ndquadrant.com>
<CAMkU=1zq2DDFnnoqK_TnFgzz7WF5SSTjvAVU7ga2Ljbpu_yECQ@mail.gmail.com>
On Tuesday, July 10, 2012 03:36:35 PM Jeff Janes wrote:
> On Tue, Jul 10, 2012 at 5:44 AM, Andres Freund <andres@2ndquadrant.com>
wrote:
> > On Tuesday, July 10, 2012 08:14:00 AM Maxim Boguk wrote:
> >> So kernel doesn't start write any pages out in background before it has
> >> at least 13Gb dirty pages in kernel memory.
> >> And at end of the checkpoint kernel trying flush all dirty pages to
> >> disk.
> >
> > Thast not entirely true. The kernel will also writeout pages which
> > haven't been written to for dirty_expire_centisecs.
>
> There seems to be many situations in which it totally fails to do that.
Totally as in diry pages sitting around without any io activity? Or just not
agressive enough?
Currently its a bit hard to speculate about all without specifying the kernel
because there have been massive rewrites of all that stuff in several kernels
in the last two years...
Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: andres@2ndquadrant.com, jeff.janes@gmail.com, maxim.boguk@gmail.com, dmk@mr-paradox.net
Subject: Re: Massive I/O spikes during checkpoint
In-Reply-To: <201207101541.18492.andres@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox