James Mills uttered:
Hi Richard,
When I mean high-traffic I would imagine more than 1 hit/s.
I do want to clear something up though (if you could):
If a site using sqlite takes 700ms to load and there are
two simultaneous (as simultaneous as one can get) hits
to the site, say user A and user B. What happens ?
Does user A get the site displayed while user B waits ?
If you have two simultaneous sessions loading, so long as the sessions are
read only, they will open in parallel (assuming you have a threaded
server.)
This is probably not a SQLite issue, rather a webapp issue.
Obviously this is a really simple scenario and with high
volume websites this could become a problem.
Also can you suggest any tips and things to think about
when designing a web app with SQLite ?
What are you using the database for? Caching? Session state management?
If you want per-session writable data, you might want to partition
session data from global data, and have the session data in separate
per-session databases. The webapp opens the global database, which
hopefully will be mostly read-only, and then ATTACHes a per-session
database for session updates.
If your global data is going to be the write bottleneck, then you may be
boned and will have to look at something like PostgreSQL. One possible way
around this is to use group commit to marshal multiple sessions' writes
to the database in a single transaction.
For further suggestions, you'll have to let people know exactly how you
intend to use the database.
Thanks again,
cheers
James
Christian
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
