Re: Rather large LA
| От | Damon Snyder |
|---|---|
| Тема | Re: Rather large LA |
| Дата | |
| Msg-id | CACkQbuh1cwyAWbZuA2ai4b478LTTHqq8jW4sB0SWv62QfdNyEw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Rather large LA (Alan Hodgson <ahodgson@simkin.ca>) |
| Список | pgsql-performance |
If you are not doing so already, another approach to preventing the slam at startup would be to implement some form of caching either in memcache or an http accelerator such as varnish (https://www.varnish-cache.org/). Depending on your application and the usage patterns, you might be able to fairly easily insert varnish into your web stack.
Damon
On Tue, Sep 6, 2011 at 12:47 PM, Alan Hodgson <ahodgson@simkin.ca> wrote:
On September 6, 2011 12:35:35 PM Richard Shaw wrote:If it's running OK after the startup rush, and it seems to be, I would leave
> Thanks for the advice, It's one under consideration at the moment. What
> are your thoughts on increasing RAM and shared_buffers?
>
them alone. More RAM is always good, but I don't see it helping with this
particular issue.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
В списке pgsql-performance по дате отправления: