My application is an apache based kiosk system that displays images. The SQLite database is used by PHP to track user info, who is logged in and what they have selected. SQLite is NOT managing anything about the files. I have a few customers that are running with 40 to 50 kiosks.
>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. Considering the SQLite database is used on page loads and when users tag images, but NOT when requesting images, I believe that 69 hits a second is more then fast enough. Am I correct or is there something else I need to be taking into consideration? 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" Sam _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
