Re: PHP + Postgres: More than 1000 postmasters produce
От | Gellert, Andre |
---|---|
Тема | Re: PHP + Postgres: More than 1000 postmasters produce |
Дата | |
Msg-id | 2740724BDE77EC4CB3CF41EA2227845730B02B@NT-VISEXCH обсуждение исходный текст |
Ответы |
Re: PHP + Postgres: More than 1000 postmasters produce
Re: PHP + Postgres: More than 1000 postmasters produce |
Список | pgsql-general |
Hi Richard, > Actually it's probably 8kB each = 16MB, but thats between > *all* the backends. > You probably want something a fair bit larger than this. Go to > http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php > and read the section on performance tuning and on the annotated > postgresql.conf I know this page and I corrected the values according to these hints, but because of the immense problems ,i set them back to the same values we use on the old servers. > You can probably put vaccum_mem back up. Because it is not rush hour now and i am leaving office for 3 days, I do this on tuesday , to have a chance to roll back if errors occur. > So - you let PHP open persistent connections to PG and have > no limit to the > number of different connections open at any one time? > Turn the persistent connections off - you'll probably find > your problems go away. I have done this before, but when i remember right, the only effect is, that every second dozens of postmaster processes started and closed, because the connection is thrown away. This helps for now, as i can see on "low traffic" , but when I tried first, we had heavy load just by starting this large number of processes. There are 5-10 php skripts running per second, in peeks maybe even twice or more. This is a problem for the system , when for every process postmaster must be started, or am I wrong ? bye Andre
В списке pgsql-general по дате отправления: