On Fri, 2005-01-14 at 13:08 -0800, Skylos wrote:
> My first suggestion based on a migration the company I work for did
> not too long ago would be to use apache2 in thread mode. There was a
> staggering drop in system memory resources consumed when we made the
> shift - from most of a gigabyte to
On Sat, 2005-01-15 at 18:31 -0700, [EMAIL PROTECTED] wrote:
> Would you recommend squid or mod_proxy?
I would recommend mod_proxy because you already know how to run apache,
and it can run useful things like mod_rewrite, mod_ssl, mod_auth_tkt,
etc. I benchmarked them a VERY long time ago and foun
rg
> Subject: Re: [BENCHMARK] Server Resources
>
> .
> >
> > Probably the biggest bang for the buck with the least effort or code
> > changes is to set up a lightweight (i.e. non-mod_perl) reverse proxy
> httpd
> > in front of the httpd that is running mod_perl:
> >
>
> Would you recommend squid or mod_proxy?
>
.
>
> Probably the biggest bang for the buck with the least effort or code
> changes is to set up a lightweight (i.e. non-mod_perl) reverse proxy httpd
> in front of the httpd that is running mod_perl:
>
Would you recommend squid or mod_proxy?
> Hey there
>
> It strikes me that your problem is directly related to memory usage.
> Linux machines have a bad problem in that if your apache children get
> swapped out ->for any reason at all<-, they will lose any shared memory
> that they may have had before being swapped out. When they are s
Skylos wrote:
My first suggestion based on a migration the company I work for did
not too long ago would be to use apache2 in thread mode. There was a
staggering drop in system memory resources consumed when we made the
shift - from most of a gigabyte to only a few hundred megs! The
site's respo
Larry Leszczynski wrote:
[...]
Probably the biggest bang for the buck with the least effort or code
changes is to set up a lightweight (i.e. non-mod_perl) reverse proxy httpd
in front of the httpd that is running mod_perl:
http://perl.apache.org/docs/1.0/guide/strategy.html#Adding_a_Proxy_Server_in
Way not enough information. Like, you can host 30 websites on a
386sx-25 with 64 megs of ram - if they're low
demand enough. It really has no relevancy to the number of sites.
Its all about how many file presentations you're handling, and more
importantly, how many dynamic script presentations y
Hey there
It strikes me that your problem is directly related to memory usage.
Linux machines have a bad problem in that if your apache children get
swapped out ->for any reason at all<-, they will lose any shared memory
that they may have had before being swapped out. When they are swapped
b
On Fri, 14 Jan 2005 [EMAIL PROTECTED] wrote:
> We have recently added a site to our server which hosts 30 other sites.
> The new site uses modperl & MySQL. After adding the new site, the server
> we were on (shared server at a national server farm) had major resource
> problems (too many connecti
Thanks for the suggestions. We are planning on migrating to Apache 2.0,
but I need to read up on the implications to the various sites first.
Do you think this server has enough resources to handle our sites without
trouble?
Sys
>>
>> But before I go any further with testing & modifying configur
No, i didn't preload the scripts - I'm not familiar with the
technique, and it seems like there's enough dynamic fvariable-writing
and storage of html values done in the scripts that large chunks would
be unfairly 'written' and cause duplication. Its a bad system design
for this volume, it should
Skylos wrote:
Also, to compare, I work with an apache 1.3 site that has alot of cgi
perl script on it. With the idea that shifting to mod_perl registry
mode would cause this site to go faster, I modified the configuration.
And watched the system load average rapidly climb into the
multiple-hundre
My first suggestion based on a migration the company I work for did
not too long ago would be to use apache2 in thread mode. There was a
staggering drop in system memory resources consumed when we made the
shift - from most of a gigabyte to only a few hundred megs! The
site's response speed pick
First let me apologize if this is not the appropriate forum for my question.
I thought it would be because the issue has to do with
apache/modperl/mysql performance.
We have recently added a site to our server which hosts 30 other sites.
The new site uses modperl & MySQL. After adding the new site
15 matches
Mail list logo
