| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | bsreejithin <bsreejithin(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How clustering for scale out works in PostgreSQL |
| Date: | 2013-08-29 16:46:06 |
| Message-ID: | 521F7ACE.5040708@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 08/29/2013 09:42 AM, bsreejithin wrote:
>
> The performance test that was conducted was for 1 Hour.
>
> There are 6 transactions. 2 DB inserts and 4 SELECTs.
> Every 2 minutes there will be 4 SELECTs. And every 3 minutes there will be 2
> DB inserts.
This shouldn't be a problem with proper hardware and a connection
pooler. The concern isn't the 1000 sessions, it is the creating and
destroying in rapid succession of 1000 connections. A connection pooler
will resolve that issue.
Sincerely,
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2013-08-29 16:49:56 | Re: How clustering for scale out works in PostgreSQL |
| Previous Message | bsreejithin | 2013-08-29 16:42:15 | Re: How clustering for scale out works in PostgreSQL |