I'm new to Apache & to my environment too.
We run 4 Apache V2.0.52 & I've seeing high load averages (of 3 to 13)
reported by "top" on the Linux RHES 4.6 for the 1, 5 & 15 minutes avgs
on 3 of our webservers. All the servers' CPU are generally idle except
one webserver which sometimes hit 90-100%
off Millikan [mailto:gmilli...@t1shopper.com]
Sent: Sunday, May 29, 2011 11:36 PM
To: users@httpd.apache.org
Subject: RE: [users@httpd] Apache 2.x configuration for high load servers
> Nor sure I understand where you say memcache is slow, we uses memcache
> for session variables and for my
t: Re: [users@httpd] Apache 2.x configuration for high load servers
mount -o noatime,nodiratime,remount /path/to/mount/point
b.
On 28 May 2011 20:13, Geoff Millikan wrote:
> I will mod fstab and reboot one server at a time...
I thought there was a way of dropping atime in real time without
@httpd.apache.org
Subject: RE: [users@httpd] Apache 2.x configuration for high load servers
> I will mod fstab and reboot one server at a time...
I thought there was a way of dropping atime in real time without a reboot so
you can test performance differences without rebooting
but I could
> Nor sure I understand where you say memcache is slow, we uses memcache
> for session variables and for mysql query caching. I did not think
> there was anything as reliable and fast or faster than that? Can you
> elaborate on file-based-cache fro mysql querrie?
Bostjan Skufca replied already h
> This went well until there were not too many files on the file system...
Our experience here has been this: We're on ext3 and caching (on disk) several
hundred thousand files using mod_disk_cache. We got
worried we were going to have too many files but using "df -i" below shows
we're at about
mount -o noatime,nodiratime,remount /path/to/mount/point
b.
On 28 May 2011 20:13, Geoff Millikan wrote:
> > I will mod fstab and reboot one server at a time...
>
> I thought there was a way of dropping atime in real time without a reboot
> so you can test performance differences without reboo
> I will mod fstab and reboot one server at a time...
I thought there was a way of dropping atime in real time without a reboot so
you can test performance differences without rebooting
but I could be mistaken. Might want to check out using relatime but I have no
experience with that. I do kno
> I commented out mod_dir and Apache would not start
Yep, you'll need that one. You probably will not need the below list but you
kinda have to read up on what each module supports and
see if you're using any of those things.
mod_userdir.so
mod_usertrack.so
mod_status.so
mod_logio.so
mod_cgi.so
r
>
> Infinity Labs Inc.
>
> (514) 387-0638 Ext: 207
>
> [image: ilabs-email-sig]
>
>
>
>
>
> *From:* Bostjan Skufca [mailto:bost...@a2o.si]
> *Sent:* Friday, May 27, 2011 12:23 PM
>
> *To:* users@httpd.apache.org
> *Subject:* Re: [users@httpd] Apache
Ext: 207
ilabs-email-sig
From: Bostjan Skufca [mailto:bost...@a2o.si]
Sent: Friday, May 27, 2011 12:23 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Apache 2.x configuration for high load servers
Hi Rob,
couple of thoughts below, please inform me if I make wrong deductions
>
> Thanks again...
>
> Rob Morin
> Systems Administrator
> Infinity Labs Inc.
> (514) 387-0638 Ext: 207
>
>
>
>
> -Original Message-----
> From: Geoff Millikan [mailto:gmilli...@t1shopper.com]
> Sent: Friday, May 27, 2011 3:35 AM
> To: users@httpd.apache.org
> S
com]
Sent: Friday, May 27, 2011 3:35 AM
To: users@httpd.apache.org
Subject: RE: [users@httpd] Apache 2.x configuration for high load servers
#Increase this number. The zombies you're seeing
#is every time an Apache child process dies.
#The child will die @1500. We run at 2 and are hav
> We also use New Relic and new PHP performance tuning tool, its very cool...
Oh, and remember to remove/comment out any PHP modules you aren't using. Every
PHP module you load (like the GD image module which
is loaded by default that people don't often use) is loaded up into the Apache
server
#Increase this number. The zombies you're seeing
#is every time an Apache child process dies.
#The child will die @1500. We run at 2 and are having no problems.
MaxRequestsPerChild 1500
#We don't run as hot as you (we average 3 hits/sec and max at like 15
#in a 24 hour period) but here's
Administrator
Infinity Labs Inc.
(514) 387-0638 Ext: 207
-Original Message-
From: Rob Morin [mailto:r...@ilabsinc.com]
Sent: Wednesday, May 25, 2011 3:00 PM
To: users@httpd.apache.org
Subject: RE: [users@httpd] Apache 2.x configuration for high load servers
Thanks for the prompt reply
On May 25, 2011 10:27 , Rob Morin wrote:
We have recently had a 30% increase in traffic and will be expecting
more. I would like to know the correct way to calculate the proper
settings for prefork.c my settings, here is what I have now...
I am going to add more RAM today to make a total of
17 matches
Mail list logo
