Note that there are some explanatory texts on larger screens.

plurals
  1. POThe ideal multi-server LAMP environment
    text
    copied!<p>There's alot of information out there on setting up LAMP stacks on a single box, or perhaps moving MySQL onto it's own box, but growing beyond that doesn't seem to be very well documented.</p> <p>My current web environment is having capacity issues, and so I'm looking for <strong>best-practices</strong> regarding <strong>configuration tuning</strong>, determining <strong>bottlenecks</strong>, <strong>security</strong>, etc. </p> <p>I presently host around 400 sites, with a fair need for redundany and security, and so I've grown beyond the single-box solution - but am not at the level of a full ISP or dedicated web-hosting company.</p> <p>Can anyone point me in the direction of some good <strong>expertise on setting up a great apache web-farm</strong> with a view to security and future expansion?</p> <p>My web environment consists of 2 redundant MySQL servers, 2 redundant web-content servers, 2 load balancing front-end apache servers that mount the content via nfs and share apache config and sessions directories between them, and a single "developer's" server which also mounts the web-content via nfs, and contains all the developer accounts. </p> <p>I'm pretty happy with alot of this setup, but it seems to be choking on the load prematurely.</p> <p>Thanks!!</p> <p>--UPDATE--</p> <p>Turns out the "choking on the load" is related to <code>mod_log_sql</code>, which I use to send my apache logs to a mysql database. By re-configuring the webservers to write their sql statements to a disk file, and then creating a separate process to submit those to the database it allows the webservers to free up their threads much quicker, and handle a much greater load.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload