Hi,
I see from an earlier post on the mason-users list that your app is
using HTML::Mason and Apache::Session::Memcached. It seems like you've
got quite a few variables to juggle in your performance bottleneck
analysis.
Actually, I am using TT and Mason in this application. TT is used to support
templates from the old version that we did not have time to port to Mason.
The part that needs the speed is the part that uses TT.
Have you tried switching to, say, Apache::Session::MySQL to see if
there
is any difference?
I used to use A::S::MySQL, but it created 2 connections for every process.
This caused 'Too many connections' error. So I tried to use memcached. Now
that I know how to make one connection per process (using database.table
identifier on all sql queries), I'll probably try to use A::S::MySQL again.
One cheap way to check for memory leaks (most probably introduced by
your perl code if they exist) is to run httpd -X (non-forking mode) and
watch the memory usage of httpd while you send some requests.
You may also want to strace the process:
# httpd -X &
# strace -o /tmp/strace.out -p `pidof httpd`
# tail -f /tmp/strace.out
Then hit the server with some requests and watch the strace output.
This is especially useful for finding I/O or IPC bottlenecks.
Hmmm... Interesting... I'll give it a try...
good luck
Thanks...
---
Badai Aqrandista
Cheepy (?)
_________________________________________________________________
Dating? Try Lavalife get 7 days FREE! Sign up NOW.
http://www.lavalife.com/clickthru/clickthru.act?id=ninemsn&context=an99&a=20233&locale=en_AU&_t=33473
