Re: [sqlite] Performance issue on records retrieval :: 100, 000 records

2009-07-16 Thread Simon Slavin
On 16 Jul 2009, at 6:22pm, MADHAVAN VINOD wrote: > Suppose, if I don't have index, is this the desired behavior of Sqlite > to take this much time to fetch just 10 records or am I missing > something here. Your first post states quite clearly '5) No INDEX created.'. Without any index on your

Re: [sqlite] Performance issue on records retrieval :: 100, 000 records

2009-07-16 Thread Pavel Ivanov
> Suppose, if I don't have index, is this the desired behavior of Sqlite > to take this much time to fetch just 10 records or am I missing > something here. You're missing that SQLite have to fetch all records satisfying your condition into memory storage, sort all these records in memory and

Re: [sqlite] Performance issue on records retrieval :: 100, 000 records

2009-07-16 Thread MADHAVAN VINOD
Hello Michal, Thanks for the reply. Please see my comments inline. >>if you always have condition a=1 (or something similar which uses = for >>comparison) you should have index which starts with this field. The possible values for this field are 1/2. And mostly all the records have the value

Re: [sqlite] Performance issue on records retrieval :: 100, 000 records

2009-07-16 Thread Michal Seliga
MADHAVAN VINOD wrote: > > 5) No INDEX created. > > The retrieval logic is such that to retrieve the oldest 10 records along > with some additional constraints (say a, b and c are columns and the > constraints are like a=1 AND b < c). > > > > So my WHERE clause is like "CurrTime <=

[sqlite] Performance issue on records retrieval :: 100, 000 records

2009-07-16 Thread MADHAVAN VINOD
Hi All, Description of my setup: My database contains 1) One table 2) 20 fields (contains date field to store the inserted time) 3) 100,000 records 4) database size is 21MB. 5) No INDEX created. 6) Sqlite version 3.5.9. The retrieval logic is such that to retrieve