Re: AW: [PEAR-DEV] RE: Re: Sqlite wrapper for Log package

Hi! Bertrand Mansion wrote:

Actually, sqlite works better with "small" databases. So it is recommended, for example with a log db, to have it "splitted" into multiple smaller dbs. For example, one per month or week, it depends on your log use. ... About the lock created on concurrent writes, I haven't tested yet but I would say it might not be noticeable as the write is done very quickly.

Well, I am not sure about this myself as I never used SQLite, but I *expect* some problems here. BTW, I looked at SQLite's speed comparison page [1] and it is a total joke: 1) The data is only ~14MB. Plaintext access log for a well-visited site will be much bigger in a *day*, not week or month. Add database overhead to this... 2) The "database" that is being promoted for web is not tested for concurrency, while web is concurrent by its nature. 3) They test with PostgreSQL's version that is 2,5 years (!) old. 4) They test PostgreSQL with default setup, which is *well-known* to be quite conservative. While the results with a more appropriate setup are also present, they are conveniently buried deep in the page. 5) I am not sure about MySQL, but version 3.23.41 does not seem too new either. [1] http://www.sqlite.org/speed.html