From: | Damon Snyder <damon(at)huddler-inc(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Rather large LA |
Date: | 2011-09-06 20:37:41 |
Message-ID: | CACkQbuh1cwyAWbZuA2ai4b478LTTHqq8jW4sB0SWv62QfdNyEw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)simkin(dot)ca> wrote:
> On September 6, 2011 12:35:35 PM Richard Shaw wrote:
> > Thanks for the advice, It's one under consideration at the moment. What
> > are your thoughts on increasing RAM and shared_buffers?
> >
>
> If it's running OK after the startup rush, and it seems to be, I would
> leave
> 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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-09-07 01:03:38 | Re: how fast index works? |
Previous Message | Anibal David Acosta | 2011-09-06 20:28:12 | Re: how fast index works? |