On 6/17/07, Thomas den Braber <[EMAIL PROTECTED]> wrote:
The problem is with the Mysql documentation, they don't share the performance an tuning information for free and if you look on the web I couldn't find much either.
I've always been able to find what I wanted in the MySQL docs. It also comes with sample my.cnf files (I think they're in /usr/share/mysql/ on Red Hat) which give guidance on tuning.
One thing I did found was that if you have more connection open Mysql has more open tables which has also a limit (open_files_limit). Maybe I have to raise that as well.
That's correct, and you may want to give it more RAM.
> > If you already have a front-end proxy, you shouldn't have a lot of > idle > > servers holding db connections. Assuming that your application uses > > the database on every mod_perl request, only processes that are > > actually sleeping will not be using their connection. You mean the because of the connection timeout in Mysql the not used connections are dropped ?
No, I mean that all of your active processes need their database handles to do work, so the only ones that would be able to give some up to a pool are the sleeping ones.
One problem is that if users upload or download files, they use the backend mod_perl for that because of authorizing an logging.
You can fix that. Here are a few ideas: - Disconnect from the database before doing the upload. Reconnect after. - Use an auth module that works without mod_perl, like mod_auth_tkt. - Use a proxy like perlbal which can ask mod_perl for an auth check and then handle the upload itself. There are undoubtedly other ways to do it, but those are the ones that spring to mind. - Perrin
