I built and use an application server which embeds Sqlite and processes
web traffic. It is multi-threaded and can handle very many connections.
It is very fast because it uses no IPC channels or process creation.
It caches threads and reuses them rather than creating and killing them.
It can use sendfile/TransmitFile access to the internet with maximum
efficiency. It sounds to be similar to what you propose.
The simplicity of Sqlite does not come free. You have to be aware of
the way it single streams access. Only one user can write to the
database at a time, but many users can read. You have to design your
application and synchronization skilfully to handle that constraint.
You may consider breaking up your data into seperate databases.
If your design handles the synchronization well your emedded Sqlite
database will handily outperform MySql or PostgreSQL. If you don't want
to be involved at that design level, use PostgreSQl.
James Mills wrote:
Hi Folks,
I'm wanting to use SQLite in an embedded web application
that will serve as a proxy and possible serve up many
connections at once. I'm talking here of high-traffic
through this web app.
Question is, how will SQLite perform under these kinds
of conditions ? I've been speaking to a few of the Trac
developers, and they inform me that SQLite uses a global
writer meaning that only a single thread can write at
any one point in time. This would explain why trac-hacks.org
is so slow at times to load up.
Thoughts/Comments ?
(btw) I really don't want to be using a server-client
rdbms such as MySQL or Postgresql because of the small
overheads in having a server.
cheers
James
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
