Re: [sqlite] Row Level Locking as in InnoDB

2013-11-08 Thread Aris Setyawan
For a single threaded application BDB is very bad after I tested. It takes nearly 2.5 times the amount of time and CPU to do a transaction of 40MB Data. E.g. If SQLIte did the 40MB data transaction (1 rows of 4 K) in 1 second, BDB was taking 2.5 seconds and more CPU as well. I did this in

Re: [sqlite] Row Level Locking as in InnoDB

2013-11-08 Thread Aris Setyawan
You use BDB SQL or BDB KV ? You must try it with SQLightning too, https://gitorious.org/mdb/sqlightning On 11/8/13, Aris Setyawan aris.s...@gmail.com wrote: For a single threaded application BDB is very bad after I tested. It takes nearly 2.5 times the amount of time and CPU to do

Re: [sqlite] Row Level Locking as in InnoDB

2013-11-08 Thread Aris Setyawan
This is the BDB SQL doc I found. http://docs.oracle.com/cd/E17076_02/html/bdb-sql/dbfeatures.html#bulkloading If you insert record in bulk, you can use PRAGMA TXN_BULK for optimization. On 11/8/13, Aris Setyawan aris.s...@gmail.com wrote: You use BDB SQL or BDB KV ? You must try

Re: [sqlite] Row Level Locking as in InnoDB

2013-11-04 Thread Aris Setyawan
Gupta raheel...@gmail.com wrote: Will SQLite4 be a better solution for me then ? Also @aris do you recommend BDB over Sqlite for 1-10 Billion records ? On Mon, Nov 4, 2013 at 8:03 AM, Aris Setyawan aris.s...@gmail.com wrote: I just looked, sophia is nothing special. See these microbench

Re: [sqlite] Row Level Locking as in InnoDB

2013-11-04 Thread Aris Setyawan
, 2013 at 6:42 PM, Aris Setyawan aris.s...@gmail.com wrote: Will SQLite4 be a better solution for me then ? SQLite4 still in development phase. It is not production ready. Also @aris do you recommend BDB over Sqlite for 1-10 Billion records ? If you have many core of processors [and big RAM

Re: [sqlite] Row Level Locking as in InnoDB

2013-11-03 Thread Aris Setyawan
SQLite do not use row level locking, but db level locking, so it was the right behavior the second thread was blocked. For innodb like in SQLite, Oracle have SQLite compatible API, but use BDB backend. Since BDB use MVCC (row/page level locking), your threads only blocked if they will write in

Re: [sqlite] Row Level Locking as in InnoDB

2013-11-03 Thread Aris Setyawan
, then test it before decide to use it. LMDB is storage engine optimized for read. Why you don't optimize it's write using cache oblivious data structure, for example LSM tree or create new, like in sophia (sphia.org) key value DB? On 11/3/13, Howard Chu h...@symas.com wrote: Aris Setyawan wrote: SQLite

Re: [sqlite] Row Level Locking as in InnoDB

2013-11-03 Thread Aris Setyawan
I just looked, sophia is nothing special. See these microbench results. http://pastebin.com/cFK1JsCN LMDB's codebase is still smaller and faster. Nothing else touches LMDB's read speed. Focus to the write number. You are using SSD or HDD? On 11/4/13, Howard Chu h...@symas.com wrote: Aris

Re: [sqlite] search

2012-01-02 Thread Aris Setyawan
with XML? Thanks, Durga. On Fri, Dec 30, 2011 at 8:05 PM, Aris Setyawan aris.s...@gmail.com wrote: Hi Durga, Another alternative, you can use an xml database. It will fix your problem easily using xquery, like this: doc('region')//country/title/text() - it will show all region you have

Re: [sqlite] search

2011-12-30 Thread Aris Setyawan
Hi Durga, Another alternative, you can use an xml database. It will fix your problem easily using xquery, like this: doc('region')//country/title/text() - it will show all region you have doc('region')//village/title/text() - it will show all village you have You also can use selection