> > Do not stay with sqlite in production
I don't agree http://www.sqlite.org/whentouse.html "SQLite usually will work great as the database engine for low to medium traffic websites (which is to say, *99.9% of all websites*). The amount of web traffic that SQLite can handle depends, of course, on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic" first comment from http://stackoverflow.com/questions/54998/how-scalable-is-sqlite : " As I mentioned in my first edit, database indexes dramatically reduce query time, but this is more of a general observation about databases than it is about SQLite. However, there is another trick you can use to speed up SQLite:transactions<http://www.sqlite.org/lang_transaction.html> ." And we know that web2py puts every request in a transaction And great advices from another comment from the same page: If you want to speed things up with SQLite, do the following: - upgrade to SQLite 3.7.x - Enable write-ahead logging<http://www.sqlite.org/draft/releaselog/3_7_0.html> - Run the following pragma: "PRAGMA cache_size = Number-of-pages;" The default size (Number-of-pages) is 2000 pages, but if you raise that number, then you will raise the amount of data that is running straight out of memory.
