My performance measurements using a modest server and a more efficient www server than Apache gives an Sqlite capability of 30-50 hits per second using simple SQL selects. Think of that as a reasonable upper limit.
Jay A. Kreibich wrote: > On Mon, Mar 24, 2008 at 03:55:12PM -0400, Sam Carleton scratched on the wall: > > >>>From the web site's "Appropriate Uses for SQLite" it says that "any >>site that gets fewer than 100K hits/day should work fine with SQLite". >> I did the math and that looks to be around 69 hits a second. > > > Try the math over: > > 24 hours * 60 minutes * 60 seconds = 86,400 seconds/day. > > 100,000 hits/day / 86,400 seconds/day = 1.1574 hits/sec (on average). > > Of course, this is on average. A real website getting "100K hits per > day" would generally expect 10x to 15x this rate during heavy times. > > That's still not ~69 hits/sec, however. > > >>As I am developing the software, is there anything I need to keep in >>mind to help optimize the database usage to achieve the million hits a >>day the "Appropriate Uses for SQLite" > > > The big thing is that locks are exclusive across the whole database, > so an application needs to get it, do what it needs, and get out. > A clean database design and proper use of indexes on critical columns > (for queries) as well as transactions (for updates) are most likely the > first places to look. > > -j > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
