Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] [announce] ocaml-sqlite 0.3.5
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2004-04-19 (15:16)
From: Mikhail Fedotov <mikhail@k...>
Subject: RE: sqlite performance [was Re: [Caml-list] [announce] ocaml-sqlite 0.3.5]

>> But more simply and importantly, SQLite only commits to the file when 
>> a transaction is completed.  (There's an implicit transaction around 
>> every INSERT / UPDATE, etc. if you don't specify a transaction 
>> yourself.) I've seen significant performance increases by wrapping 
>> repeated modifications of large datasets with transactions (by using 
>> the SQL statements "BEGIN;" and "END;"), which allows the disk access 
>> to be

>I've read this FAQ before on the sqlite site, but it doesn't apply to my
>case: I've a database which is static, it is built from scratch from time
>to time and I simply need to perform a lot of SELECT on the db.

A trivial suggestion, but this usually comes from absence of
indexes or sql queries which fail to use existing indexes. I.e.
you have a good reason to check how your sql queries are
compiled into sqlite virtual machine instructions.

This was discussed in the sqlite list from time to time.


To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: