httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Morin <...@ilabsinc.com>
Subject RE: [users@httpd] Apache 2.x configuration for high load servers
Date Mon, 30 May 2011 12:05:35 GMT
I understand what your saying... I am not part of the dev team nor do I have
any PHP programming skills beyond test pages and very crude scripts. I do
know that if we were to turn off memcache, our DB server would skyrocket in
load and bring our site to a halt almost and put hugs loads on the server.
>From what I understand, the dev guys store almost everything that can be
stored in the DB.... allot of the queries are unique too, not sure how that
works with mod_cache??  I will also check up on Xdebug and see how that
works from within our code and read up more on mod_cache...

Thanks for all you help guys, its been really appreciated..

And a df -I on one of my web servers looks like this...

Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/sda5            77070336  574507 76495829    1% /
/dev/sda2             524288      43  524245    1% /tmp
/dev/sda1              26104      47   26057    1% /boot
tmpfs                2054442       1 2054441    1% /dev/shm
tmpfs                2054442    1612 2052830    1%
/var/cache/php-eaccelerator/RAM



Rob Morin
Systems Administrator
Infinity Labs Inc.
(514) 387-0638 Ext: 207




-----Original Message-----
From: Geoff Millikan [mailto:gmillikan@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 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 however I'll say that mod_disk_cache is a
great tool.  But only on those pages which are high
traffic, dynamic and most importantly are not customized based on session or
IP address.   You would not need to use any other
caching tools like memcache - because the preassembled, compressed/zipped
page is already assembled, sitting on disk - the page is
just read off the disk and sent to the clients.  Queries will not be run,
code will not be executed - basically you're serving a
static page right off the disk.  

You can see how this would both speed up the serving of the page and free up
the database (and RAM) to do other things.  

Thanks,

Geoff Millikan @ http://www.t1shopper.com/


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org



---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message