From: | Praveen Mishra <cordialpraveen(at)gmail(dot)com> |
---|---|
To: | pgadmin-support(at)postgresql(dot)org |
Subject: | Performance issue when using pgpool for fail-over and recovery of postgresql DB |
Date: | 2013-05-09 05:27:00 |
Message-ID: | 1368077220363-5754820.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
I am working on a POC of setting up PGPOOL with postgresql for failover and
recovery.
Everything is working fine but I am observing huge performance delay with
transaction.
Following is my setup..
PGPOOL : Running on separate Amazon Instance (Used for fail-over and
recovery[No loa balancing and streaming replication])
POSTGRESQL DB: Setup on two different Amazon Instance with streaming
replication setup .
Application Server: Apache running on separate Amazon Instance and connect
to pgpool which intern connected to postgresql servers.
In normal scenario where Apache is directly connected to postgresql it takes
5 -7 seconds to complete the transaction...
But if I am connecting through pgpool it is taking more than 40 seconds to
complete the transaction.
Note: How can I change the log level (PGPOOL logs all the statements tried
to change the log level but it does not work)
Please help me with the possibilities how can i improve the performance
Regards,
Praveen
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Performance-issue-when-using-pgpool-for-fail-over-and-recovery-of-postgresql-DB-tp5754820.html
Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2013-05-09 06:02:23 | Re: 1.16.1: many operations cause display tree to collapse |
Previous Message | Aren Cambre | 2013-05-09 02:20:40 | Re: 1.16.1: many operations cause display tree to collapse |