On 25 Sep 2011, at 3:33pm, Artyom Beilis wrote: > That several users accessing same DB from several processes can't > perform more then 10 transactions per second...
Roughly how many commands are in each transaction ? Are we talking tens or hundreds or thousands ? Roughly how many concurrent users do you have ? How is access to your database shared ? Are all your users opening the database across a network using a Windows share ? You might already know this, but SQLite does not support any locking except by locking the entire database. So if one use has a transaction half way through writing, no other users can do anything. There's nothing you can do about this with any combination of hacks. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
