gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] postgresql considerations


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] postgresql considerations
Date: Thu, 14 Jun 2012 19:56:42 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Jun 14, 2012 at 04:07:22PM +0200, Hilbert, Sebastian 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.

- many small queries in a use case which would benefit from fewer
  larger queries
- one large query in a use case which would benefit from many
  smaller queries

- network latency
- wire transmit capacity

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

[Prev in Thread] Current Thread [Next in Thread]