[Top][All Lists]

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

[GNUnet-developers] Re: dropping support for SQlite from GNUnet due to b

From: Christian Grothoff
Subject: [GNUnet-developers] Re: dropping support for SQlite from GNUnet due to bug? workaround?
Date: Sun, 21 Aug 2005 15:28:44 -0700
User-agent: KMail/1.7.2

Thanks a lot, this solves the issue (we're now using 10 MB memory total for 
everything -- where before it went up to 1 GB and possibly more).  


On Sunday 21 August 2005 14:40, D. Richard Hipp wrote:
> On Sun, 2005-08-21 at 14:21 -0700, Christian Grothoff wrote:
> > First of all, thanks for the quick response.  You suggested adding an
> > index, however we do have an index on all of the colums.  Als Nils
> > pointed out in a private E-mail to me, the index only works for equality
> > constraints, as in
> >
> > your suggestion:
> >
> > However, our query looks like this:
> >
> > SELECT * FROM tbl
> >    WHERE (e > :4 AND p == :5) OR p > :6
> >    ORDER BY p ASC e ASC h ASC
> >    LIMIT 1
> >
> > The index is created with:
> >
> > CREATE INDEX idx_h ON tbl (h)
> > CREATE INDEX idx_p ON tbl (p)
> > CREATE INDEX idx_e ON tbl (e)
> >
> > Maybe something is wrong with the way we create the index? (should we
> > create one "big" index on h,p,e instead?)
> There is an enormous difference between three separate indices each on
> separate fields, and a single index on all three fields.  That fact is
> true for all SQL database engines, not just SQLite.  Further more, when
> you have a single index with multiple columns, the order of the columns
> is critical.  Again, this is true of all SQL database engines (that I
> am aware of) not just SQLite.
> For the query above, your index should be:
>     CREATE INDEX idx1 ON tbl(p,e,h);
> The order of the columns in the index should match the order
> of the terms in the ORDER BY clause.
> For SQLite, the performance of your query might be enhanced
> if you code it as shown below.  Unlike all of the previous
> advice I have given you, the following trick is SQLite-specific
> and will not necessarily work or help on other database engines:
>    SELECT * FROM tbl WHERE rowid IN
>      (SELECT rowid FROM tbl
>       WHERE (e>:4 AND p=:5) OR p>:6
>       LIMIT 1)
> Depending on your parameters and the data in your table,
> this latter query might run in O(N) time whereas your
> original seems likely to run in O(NlogN) time.

reply via email to

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