Alexander Batyrshin wrote:
Hello John,
Right now i am using apache + fcgid (fast-cgi).
I will try to keep database handler open. But i need to implement it,
because i am using now more than 200 databases.
That means keeping open 200 connections if you want to maximize
performance by exploiting
Hello John,
Right now i am using apache + fcgid (fast-cgi).
I will try to keep database handler open. But i need to implement it,
because i am using now more than 200 databases.
On Jan 24, 2008 9:38 PM, John Stanton <[EMAIL PROTECTED]> wrote:
> Using Apache is the problem. The connections are no
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
Hello Alexander,
I can't really comment about those modules. I have no experience with them.
-Clark
- Original Message
From: Alexander Batyrshin <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Thursday, January 24, 2008 9:24:39 AM
Subject: Re: [sqlite] Cache for SQL
Hello Clark,
I am using Apache + Fast-CGI :)
But my next move will be to mod_perl.
Currently I have only idea to use something like
Cache::SharedMemoryCache or Cache::Memcached for implementing caching
inside my application.
What are you thinking about this?
If you have any interesting ideas or kno
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
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 s
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
8 matches
Mail list logo
