Using Apache is the problem. The connections are not persistent so
caching is destroyed. It sounds like you are using CGI, and that makes
it more so. Somevariant like fastcgi (?) might give you what you look for.
Clark Christensen wrote:
I don't think you're going to get the kind of caching you want using Perl and a
web server (Apache, right?). There's just no persistence across processes, no
shared memory, no database connections.
Now, Apache's mod_perl and some associated modules could get you all that and
more. For me, anyway, it requires a big adjustment in the way you build your
apps if you want to take advantage of the shared $dbh, shared variables, and
caching. For me, the investment isn't quite worth the benefit.
-Clark
----- Original Message ----
From: Alexander Batyrshin <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Thursday, January 24, 2008 7:19:47 AM
Subject: Re: [sqlite] Cache for SQLite
On
Jan
24,
2008
4:03
PM,
Doug
<[EMAIL PROTECTED]>
wrote:
I
don't
know
of
a
daemon,
but
based
on
someone
else's
post
where
they
described
keeping
a
pool
of
sqlite3*
handles
to
the
database,
and
always
reusing
the
most
recently
used
handle
first
(so
that
the
SQLite
page
cache
is
most
likely
still
valid)
I
saw
a
very
big
jump
in
performance.
Perhaps
that
would
help
in
your
case
too?
Sounds
interesting,
maybe
it
help
me
a
little.
I
am
using
Perl
DBD::SQLite,
so
i
need
some
investigation
how
this
library
work.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
