-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robel Girma wrote: > but rather trying to > find out if my app will work with SQLite.
SQLite will definitely work and at the very least you will it useful during (rapid) development and demos. Quite simply SQLite will get you results far quicker than server based approaches which have to marshal the data across the network. > in reality, the web app will be doing all the writing and reading to SQLite. It depends very strongly on how the app is structured and in particular if there are a few persistent connections to the SQLite database, or if each request involves a separate connection to the database. If you have lots of connections then there will be contention. If the work done during contention is quick and simple then you are fine. If it is long running then you will benefit from a server based approach. But when you have commits then disk access is serialized and you will have performance limitations no matter what the database server or SQLite. (That is the point Florian is making.) > I'm trying to avoid using a traditional database server if SQLite can handle > this. I wanted to check here first for guidance to see if SQLite can do > this. I'd suggest just going ahead and doing a mock implementation and see what you get. If you have a URL that does representative work then you can use tools like ab (the Apache Benchmark tool that comes with Apache but works with any server) to run the number of concurrent requests you specify. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkowsQoACgkQmOOfHg372QQsRQCeIHiikyM8k/h/oTeitLCPzHpA IaYAoM9dEjvqD2GZWIkiWZCnni2H28GH =LzSr -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
