Re: slow performance problems: Setting processes per-user limits for daemons (such as postgres, interchange, etc.)
От | ghaverla@freenet.edmonton.ab.ca |
---|---|
Тема | Re: slow performance problems: Setting processes per-user limits for daemons (such as postgres, interchange, etc.) |
Дата | |
Msg-id | Pine.A41.3.95.1000913212150.23096A-100000@freenet.edmonton.ab.ca обсуждение исходный текст |
Ответ на | slow performance problems: Setting processes per-user limits for daemons (such as postgres, interchange, etc.) ("Dan Browning" <danb@cyclonecomputers.com>) |
Список | pgsql-novice |
On Wed, 13 Sep 2000, Dan Browning wrote: > How do I set maximum number of concurrent processes for users that run > daemons, such as postgreSQL (under postgres user), or interchange, or mysql, > or anything for that matter. limits.conf edits by themselves don't work. Kurt Seifried recently wrote a little blurb about PAM in SysAdmin, but it looks like you've already explored that area. It might help to keep plugging away at that, because it sure looks like a finer grained way to impose limits on processes. Of course, PAM can only control processes which are linked against libpam. Does postgres even call libpam anywhere? If it doesn't, maybe you can find a way to call it somewhere. The 256 processes per user sounds suspiciously like a 8 bit counter somewhere in kernel space. There has been effort to increase a whole bunch of Linux limits to make it more enterprise-ready, some of these things are available as patches against the 2.2 kernel series, but you might need to wait for the 2.4 series, unless you want to try a 2.3 kernel. Does it help to try and keep your connections to postgres "persistent"? Gord Matter Realisations http://www.materialisations.com/ Gordon Haverland, B.Sc. M.Eng. President 101 9504 182 St. NW Edmonton, AB, CA T5T 3A7 780/481-8019 ghaverla @ freenet.edmonton.ab.ca
В списке pgsql-novice по дате отправления: