Re: Impact of checkpoint_segments under continual load conditions - Mailing list pgsql-performance

From Christopher Petrilli
Subject Re: Impact of checkpoint_segments under continual load conditions
Date
Msg-id 59d991c405072008523c6914bc@mail.gmail.com
Whole thread Raw
In response to Re: Impact of checkpoint_segments under continual load conditions  (Christopher Petrilli <petrilli@gmail.com>)
List pgsql-performance
On 7/19/05, Christopher Petrilli <petrilli@gmail.com> wrote:
> On 7/19/05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Christopher Petrilli <petrilli@gmail.com> writes:
> > > On 7/19/05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > >> How *exactly* are you invoking psql?
> >
> > > It is a subprocess of a Python process, driven using a pexpect
> > > interchange. I send the COPY command, then wait for the '=#' to come
> > > back.
> >
> > Some weird interaction with pexpect maybe?  Try adding "-n" (disable
> > readline) to the psql command switches.
>
> Um... WOW!
> It doesn't stay QUITE that low, but it stays lower... quite a bit.
> We'll see what happens over time.

here's a look at the difference:

http://blog.amber.org/diagrams/pgsql_readline_impact.png

I'm running additional comparisons AFTER clustering and analyzing the tables...

Chris
--
| Christopher Petrilli
| petrilli@gmail.com

pgsql-performance by date:

Previous
From: Dirk Lutzebäck
Date:
Subject: Optimizer seems to be way off, why?
Next
From: Christopher Petrilli
Date:
Subject: Re: Impact of checkpoint_segments under continual load conditions