Thanks for the response about how to fine tune postgres - that's some good documentation there, and I certainly appreciate what you've found in your work.
Darren
On Thu, Mar 8, 2018 at 12:28 PM, C. R. Oldham <cro@ncbt.org> wrote:
Greetings,
However, I still see where the database at times can run VERY hot.
We have set up this server to run with PostgreSQL. When I do a ps aux | grep postgres, I find a lot of processes that have been spawned to take care of mailman - a dozen or so.
Out of the box Pg performs pretty well but still benefits from tuning. Recommend you head over to https://wiki.postgresql.org/wi ki/Tuning_Your_PostgreSQL_Server and see what makes sense for your configuration.
Anectodally, at my work we produce an app with Pg as the backend database. Simple tuning, including turning
synchronous_commitoff, yielded us 10x better performance. Granted, our app is very write-heavy and typically Mailman and friends will be far more read-heavy, so giving Pg enough RAM for in-memory sorts and caching will benefit you more.--cro
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/