Your writing transactions most probably will not block readers, but each writer will block others. So whether SQLite is applicable for you depends on how much load your server will have. If it's 60/80 per second (I wouldn't call such site small :) ) then you can try it but it's already a boundary value if not over it already. Because unless you turn off synchronization with disk SQLite can do not so much writing transactions per second (actual numbers depend on hardware and file system settings). So assuming that besides your application there's others working on the same server you will feel a lot of contention for the disk I/O.
Pavel On Thu, Oct 29, 2009 at 9:27 AM, Sebastian Bermudez <sebastian.bermu...@yahoo.com> wrote: > i have an very small web site ( 60/80 Concurrent users )... running with > mysql...... but i need transactions.... ( and my web hosting does not support > innodb ).... > but have support for SQLITE 2.x & 3.x)....... > > The web site has built with PHP using PDO...... the max..db-load for a > request....is.... around 8 SELECT querys on single tables by Primary > key....(Integer field)... > Has anyone used SQLITE in a comparable environment ??? > can i replace the DB ??? > there are max..of 10 concurrent writers ( on single tables too)...( 4/7 > Insert or Update per request....) in this point i need transactions ! > > In sqlite transactions blocking readers ??? > > There are case studies for web sites using sqlite ?? > > > Yahoo! Cocina > > Encontra las mejores recetas con Yahoo! Cocina. > > > http://ar.mujer.yahoo.com/cocina/ > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
