On 7 Sep 2014, at 3:49am, Keith Medcalf <kmedc...@dessus.com> wrote:
> You say "the database connection". Did you use the language imprecisely or > are you using only one database connection? One presumes that you may have > half-a-million pages and half-a-billion concurrent HTTP operations, in which > case you will have significant multi-leaving of operations. Or is your server > single threaded and can only answer one HTTP operation at a time? Apache creates a separate process to reply to each page request. If you have Apache replying to half-a-billion concurrent HTTP requests, you will have half-a-billion processes. (Presumably on many different computers in a web farm.) If you're using PHP to access your SQLite database file, each process would open its own connection to the database. That's how it works, and it works fine on small and medium-power web hosts. That many connections would be impossible for SQLite, of course. But if your web host has half-a-billion concurrent HTTP operations your multiple web hosts will be using Postgres or some other client/server DBMS, not SQLite. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
