On Apr 1, 2005 3:53 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> > What seems to happen is it slams into a "wall" of some sort, the
> > system goes into disk write frenzy (wait=90% CPU), and eventually
> > recovers and starts running for a while at a more normal speed.  What
> > I need though, is to not have that wall happen.  It is easier for me
> > to accept a constant degredation of 5%, rather than a 99% degredation
> > for short periods, as it can cause cascade problems in the system.
> Could this possibly be a checkpoint happening?
> Also how many checkpoint segments do you have?

Changes to the postgresql.conf file from "default":

    maintenance_work_mem = 131072
    fsync = false
    checkpoint_segments = 32

I set the checkpoint segments up until it no longer complained about
them rolling over.  That was the best "advice" I could find online. 
The maintenance_work_mem I upped to deal with indexes being updated
constantly.  And finally, since I'm willing to risk some loss, I
turned fsync off, since the system is on a UPS (or will be in
production) and carefully monitored.

I did actually wonder about the checkpoint_segments being an issue,
since it seems to me the more of them you have, the more you'd have to
deal with when checkpointing, and so you might actually want to turn
that number down to create a "smoother" behavior.

Unfortunately, the alot advice for 'loading data' doesn't apply when
you have a constant stream of load, rather than just sporadic.  Any
advice is more than appreciated.

| Christopher Petrilli

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to