Problems with mod_python deployment

I went ahead with the mod_python deployment at 6.30 am this morning as planned; however it didn’t work out so I had to rollback.

The problem was that I ran out of MySQL database connections. I’ve got 120 processes and many of these processes will need MySQL connections. However only 1 in 10 requests are for CherryPy, the others are for static content so I could easily get by with only 12 processes if I was serving my static content on another server.

It’s also quite a waste of resources to be loading up lots of heavy Apache processes with both mod_php and mod_python when the vast majority of the time they are just doing images.

So, the new plan is to use lighttpd for the static content and then an Apache with ServerLimit and MaxClients set to 12.

I’ll try again tomorrow.

Leave a Reply

You must be logged in to post a comment.