[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] postgresql considerations
From: |
Sebastian Hilbert |
Subject: |
Re: [Gnumed-devel] postgresql considerations |
Date: |
Thu, 14 Jun 2012 16:07:22 +0200 |
User-agent: |
KMail/4.9 beta1 (Linux/3.2.0-24-generic-pae; KDE/4.8.80; i686; ; ) |
On Thursday, June 14, 2012 03:58:52 PM Karsten Hilbert wrote:
> > I was wondering what influences GNUmed's performance with regards
> > to database performance most.
>
> The proper answer to this question can really only be found by actual
> investigation.
>
> Possible reasons are:
>
> - network latency
> - many small queries in a use case which would benefit from fewer
> larger queries
> - one large queries in a use case which would benefit from many
> smaller queries
> - server capability (RAM, disk throughput)
> - dark buffers
> - wire transmit capacity
> - connection setup time (we only ever use one read-only connection
> per thread during app instance lifetime, though, so that would
> only affect write queries)
> - missing indices in the database
> - unfortunate joins on behalf of the query planner
> - unfortunate table layout
> - bad statistics of data distribution in the database
>
What do you think has the biggest impact ? Internet client needs roughly 10
times to get and display the data compared to the LAN/same-host client.
Sebastian