Search Postgresql Archives

Re: Major Performance decrease after some hours

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Peter Bauer wrote:
[...]
There are 10-15 postmaster processes running which use all the CPU power.
A restart of tomcat and then postgresql results in the same situation.
Some postgres processes are in DELETE waiting or SELECT waiting.
VACUUM runs through in just about 1-2 seconds and is run via cron
every minute and reports that the fsm setting are high enough.

Pure speculation: are you sure you aren't vacuuming too agressively?
The DELETE waiting and SELECT waiting sound to me like they are waiting for a lock that another vacuum is holding. You've said that you spawn a vacumm process by cron every minute, that may be fine when the server isn't too loaded. But when vacuums begins to take longer cron will spawn more and more vacuums killing your machine.

I'll add a little check in the cron script to see if there isn't already a vacuum process running or use an idependant script,
while [ 1 ]
  do
	vacuum --all
	sleep 60
  done

[...]

HTH,
--
MaXX


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux