Hi all,
after searching for a while without finding an answer to my question
I hope you can help me,
We're using mod_perl with ModPerl::Registry to have only a thin
layer between apache and our perl scripts. So far so good.
Now we want to produce error documents dynamically and thought
this could
On Mon, Sep 28, 2009 at 3:19 PM, Justin Wyllie
wrote:
> But I'm struggling to understand why my processes are so huge. Using top
> with the DATA field that shows that almost all the 90 mbs is data not
> executable code. If this is the correct interpretation of that?
Probably not. Perl code looks
Justin, I cannot have a good suggestion how to find out what hogs the
memory.
However, I want to mention that with the use of a good reverse proxy server,
you will not need to have very many apache instances running, because the
proxy server would take care of the slow interaction with the client'
Hi
I've been attempting to fine-tune my server.
The apache/mod_perl processes are around 90 Mbs - to start with.
I've preloaded a lot of code in the startup file and that makes the shared
memory space about 6 Mb. I can now see how my processes do not grow due to code
being loaded when it is r
On 09/27/2009 02:48 AM, 叶孤城 wrote:
One of our customers run a small site (about 3000 IP each day),
written with Perl CGI originally.
Now to expand some features and improve the performance, they want to
upgrade the site.
So do you think which is better that it will be re-written with pure
modper
