| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Catalin Iacob <iacobcatalin(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How to keep queries low latency as concurrency increases |
| Date: | 2012-11-26 07:46:33 |
| Message-ID: | 50B31E59.9050004@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 25.11.2012 18:30, Catalin Iacob wrote:
> So it seems we're just doing too many connections and too many
> queries. Each page view from a user translates to multiple requests to
> the application server and each of those translates to a connection
> and at least a few queries (which are done in middleware and therefore
> happen for each and every query). One pgbouncer can handle lots of
> concurrent idle connections and lots of queries/second but our 9000
> queries/second to seem push it too much. The longer term solution for
> us would probably be to do less connections (by doing less Django
> requests for a page) and less queries, before our deadline we were
> just searching for a short term solution to handle an expected traffic
> spike.
The typical solution to that is caching, see
https://docs.djangoproject.com/en/1.4/topics/cache/.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Syed Asif Tanveer | 2012-11-27 07:47:03 | Postgres configuration for 8 CPUs, 6 GB RAM |
| Previous Message | Catalin Iacob | 2012-11-25 16:30:04 | Re: How to keep queries low latency as concurrency increases |