I think Albannach is on the right track. You should step
back and take stock of your entire system and its
performance. Not just Perl. What other applications does
your server run? It is more likely that some other process
or shortage of bandwidth/storage/memory may be the problem.
Does your server also run NNTP? We use to run a news server
on our "web" box and finally had to shut it down because it
soaked too many resources (disk space, CPU cycles and
bandwidth).
Are you running sendmail on it? A couple of our
boxes were shut down for a few days because holes in
our sendmail daemons allowed spammers to use it as a relay
for hundreds of thousands of messages. The effect was
gradual not instantaneous. We had to install TCP wrappers
to close the holes.
You might want to talk to the System Administrator and find
out if they have time accounting activated or can use tools
like top to monitor allocated process resources).
If you are running a web server, you might want to check
out the message and error logs for potential problems. You
can probably generate some connection statistics via the web
server administration utilities. Our Netscape server
periodically chews up cycles for no apparent reason and has
to be stopped and restarted.
Occasionally our backups run at times they shouldn't and
slow down the system enough to generate complaints from
our Web Services department.
Hope these suggestions yield some results.
|