On 13 Nov 2005, at 23:46, Brett Randall wrote: Does anyone else have any ideas as to how I can utilise persistent database connections to a MySQL server via DBI, in order to speed up web queries, but without the 20 or so connections per virtual server that sit there waiting for something to
Leo Lapworth wrote:
Put all your virtual hosts in one database, just start the table names
differently
so instead of virtual_db.tablename have application_db.virtual_tablename
This way apache only have to connect to one database.
There may be all sorts of reasons you don't want to do this -
I'm uncertain what you are telling here because I can use different
databases while connected in a connection using the
1. Connect 2 DB (e.g. test)
2. Query: SELECT * FROM db1.tab1
3. Query: SELECT * FROM db2.tab1
So there's no need to move all tables into one database, simply connect
always to
On Mon, 14 Nov 2005, Philip M. Gollucci wrote:
Leo Lapworth wrote:
Put all your virtual hosts in one database, just start the table names
differently
so instead of virtual_db.tablename have
application_db.virtual_tablename
This way apache only have to connect to one database.
There may
On 14 Nov 2005, at 08:36, Tom Schindl wrote:I'm uncertain what you are telling here because I can use differentdatabases while connected in a connection using the1. Connect 2 DB (e.g. test)2. Query: SELECT * FROM db1.tab13. Query: SELECT * FROM db2.tab1So there's no need to move all tables into
Hi ,
We have very similiar problem.
Try to set-up mysql timeout per connection like this :
wait_timeout=100 ( or other suitble time for you )
interactive_timeout=100 ( or other suitble time for you )
in my.cnf
If a connection is idle more than 100 seconds mysql will kill a
connection. Next
On Mon, 2005-11-14 at 09:36 +0100, Tom Schindl wrote:
I'm uncertain what you are telling here because I can use different
databases while connected in a connection using the
1. Connect 2 DB (e.g. test)
2. Query: SELECT * FROM db1.tab1
3. Query: SELECT * FROM db2.tab1
So there's no need
G'day all - this
is my first post to this list. Hope what I write makes
sense...
I have a mod_perl
1.29 app running on Apache 1.3.31 - it utilises startup scripts as
such:
httpd.conf:
VirtualHost aa.bb.cc.dd...
PerlRequire
/var/www/ors/demo/startup.pl Directory
On Mon, 14 Nov 2005 10:46:56 +1100
Brett Randall [EMAIL PROTECTED] wrote:
Does anyone else have any ideas as to how I can utilise persistent
database connections to a MySQL server via DBI, in order to speed up
web queries, but without the 20 or so connections per virtual server
that sit there
Frank Wiles wrote:
3) Try things without Apache::DBI. In some situations Apache::DBI
and persistant connections are crucial, but I have found with
several apps in the past that it made little to no difference
in the end user experience. It is at least worth a try to see
On Mon, 2005-11-14 at 10:46 +1100, Brett Randall wrote:
Does anyone else have any ideas as to how I can utilise persistent
database connections to a MySQL server via DBI, in order to speed up
web queries, but without the 20 or so connections per virtual server
that sit there waiting for
11 matches
Mail list logo
