| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | sdv mailer <sdvmailer(at)yahoo(dot)com> |
| Cc: | Rod Taylor <pg(at)rbt(dot)ca>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com>, steve(at)blighty(dot)com, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL pre-fork speedup |
| Date: | 2004-05-06 16:37:41 |
| Message-ID: | 200405061637.i46Gbfe05942@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
sdv mailer wrote:
> Hi Bruce,
>
> Sorry for the confusion because Rod asked a question
> and I answered too quickly. This is what I mean.
>
> 15x Slower:
> -----------
> Client <--TCP--> PgPool <--UNIX--> PostgreSQL
> Client <--TCP--> PgPool <--TCP--> PostgreSQL
>
> 5x Faster:
> ----------
> Client <--UNIX--> PgPool <--UNIX--> PostgreSQL
> Client <--UNIX--> PgPool <--TCP--> PostgreSQL
>
>
> Hope this helps! Pgpool speeds up connection time by
> 5x with UNIX socket due to pre-fork and connection
> pooling. However, pgpool slows down by 15x under TCP
> socket for some unknown reason.
How does this compare to using tcpip without pgpool? Is it the tcp
startup/shutdown time that is hurting performance?
pgpool is using persistent connections so I don't think a difference
would show up there, but the client/pgpool connections are being
created/destroyed frequently.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-06 16:37:57 | Re: Bug in pg_dump 7.4 |
| Previous Message | sdv mailer | 2004-05-06 16:19:56 | Re: PostgreSQL pre-fork speedup |