RE: Improving server performance with mod_perl 1.29 and DBI

2005-11-14 Thread Rumen Palov
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 tim

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-14 Thread Leo Lapworth
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 one

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-14 Thread Clinton Gormley
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

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-14 Thread Fred Moyer
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 .tablename have application_db._tablename This way apache only have to connect to one database. There may be all sorts of r

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-14 Thread Tom Schindl
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 o

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-14 Thread Philip M. Gollucci
Leo Lapworth wrote: Put all your virtual hosts in one database, just start the table names differently so instead of .tablename have application_db._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 - and from a design

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-14 Thread Leo Lapworth
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 happen?

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-13 Thread Perrin Harkins
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 som

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-13 Thread Philip M. Gollucci
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 if

Re: Improving server performance with mod_perl 1.29 and DBI

2005-11-13 Thread Frank Wiles
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 si