Re: MusicBrainz postgres performance issues
| От | Ilya Kosmodemiansky |
|---|---|
| Тема | Re: MusicBrainz postgres performance issues |
| Дата | |
| Msg-id | CAG95seXv4EKGhDV04rkk_ARgvz8OQUJy3Xbx5Rw16Wxm3+1j5Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: MusicBrainz postgres performance issues (Andres Freund <andres@2ndquadrant.com>) |
| Ответы |
Re: MusicBrainz postgres performance issues
|
| Список | pgsql-performance |
On Sun, Mar 15, 2015 at 8:20 PM, Andres Freund <andres@2ndquadrant.com> wrote: > On 2015-03-15 11:09:34 -0600, Scott Marlowe wrote: >> shared_mem of 12G is almost always too large. I'd drop it down to ~1G or so. > > I think that's a outdated wisdom, i.e. not generally true. Quite agreed. With note, that proper configured controller with BBU is needed. > A new enough kernel, a sane filesystem > (i.e. not ext3) and sane checkpoint configuration takes care of most of > the other disadvantages. Most likely. And better to be sure that filesystem mounted without barrier. And I agree with Scott - 64MB work mem AND max_connections = 500 is a recipe for disaster. The problem could be in session mode of pgbouncer. If you can work with transaction mode - do it. Best regards, Ilya Kosmodemiansky, PostgreSQL-Consulting.com tel. +14084142500 cell. +4915144336040 ik@postgresql-consulting.com
В списке pgsql-performance по дате отправления: