[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Postgres query / display speed was Re: Release Candid
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Postgres query / display speed was Re: Release Candidate 1.0.rc3 |
Date: |
Wed, 21 Sep 2011 17:06:59 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Sep 21, 2011 at 12:16:08PM +1000, Richard wrote:
> This shouldn't be a problem in practice Jim - I just ran my postres drug
> view
> (admittedly not your database), some 10,000 items in the complex multi-table
> view took about 6 seconds over the network.
Same here for ref.consumable_substance.
> Doing an instring search on a single letter producing 8000 results * 60
> fields
> each took about 4 seconds, but doing an instring search on 3 letters like
> '%amo%' took <100msec, once you've typed eg amoxi takes <30msec. And all
> that
> without anything more than a primary key, no other indexes on any of the
> table
> fields.
>
> Hence presuming your search routines using a delay timer which only flicks
> off
> the query to the server once the user stops typing
Which is exactly what we do in the phrasewheels - this being
due to what Richard suggested doing many moons ago.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Re: [Gnumed-devel] Release Candidate 1.0.rc3, Jim Busser, 2011/09/21