[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Re: low performance
From: |
Horst Herb |
Subject: |
Re: [Gnumed-devel] Re: low performance |
Date: |
Mon, 7 Jun 2004 12:46:31 +1000 |
User-agent: |
KMail/1.6.2 |
On Mon, 7 Jun 2004 11:07, sjtan wrote:
> > Also, currently gnumed establishes a separate TCP connection for every
> > commit transaction,
> > a obvious and simple point for optimisation.
>
> I thought there was connection pooling.
There is connection pooling for read-only connections.
Transactions are committed at a *connection* level, a stupid limitation of the
backend libraries. A connection does not allow isolated concurrent
transactions, and pooling writeable connections would require disciplined
formal release of the connection after the transaction has been completed.
Maybe we should have another look at SQL Relay.
Horst
- [Gnumed-devel] re: low performance, sjtan, 2004/06/06
- [Gnumed-devel] Re: low performance, sjtan, 2004/06/06
- Re: [Gnumed-devel] Re: low performance,
Horst Herb <=
- Re: [Gnumed-devel] Re: low performance, Ian Haywood, 2004/06/07
- Re: [Gnumed-devel] Re: low performance, Sebastian Hilbert, 2004/06/07
- Re: [Gnumed-devel] Re: low performance, Jim Busser, 2004/06/08
- Re: [Gnumed-devel] Re: low performance, Karsten Hilbert, 2004/06/08
- Re: [Gnumed-devel] Re: low performance, Karsten Hilbert, 2004/06/08
- Re: [Gnumed-devel] Re: low performance, Horst Herb, 2004/06/08
- Re: [Gnumed-devel] Re: low performance, Karsten Hilbert, 2004/06/14