> Postgres initially worked wonderfully, fast and solid.  It
> preformed complex joins in 0.01secs, and was able to keep up with our
> message queue.  It stayed this way for almost a year during our
> development.
> Recently it started eating up the cpu, and cannot keepup with the system
> like it used to.  The interesting thing here is that it still runs great
> on an older system with less ram, one slower cpu, and an older disk.

This really points to a maintenance problem.  How often do you run VACUUM 
ANALYZE?   You have a very high rate of data turnover, and should need to 
VACUUM frequently.

Also, what's you max_fsm_pages setting.

-Josh Berkus
 Aglio Database Solutions
 San Francisco

---------------------------(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