On 07/23/2003 10:28 AM, Matt Schroebel wrote:
Is anyone using a php/mysql/apache CMS (either custom or open source) that is performing well serving on the order of 1 million page views a month with 2600+ items of content? If so, I'd like to know what your using and a description of your server setup, such as if the backend runs on a different server then the frontend, whether the DB server is separate, memory and CPU speeds. Thanks
For such high loads, I recommend that you use the *page fault technique* if each page does not have any personalization (showing different things to different users).
This consists of starting with no pages except from indexes with links to the URLs of the article pages. When the first user accesses a page, since it will not exist, the page is handled by the Web server error document page.
That page should be an actual script that maps the requested URL in fault to a parallel URL that serves the real page content. Then the error document script should fetch the content and store it in the file of the missing page. So, next time the page is accessed it will be served at the maximum speed because it already exists in static format.
The advantage of serving pages statically is that there is a miriad of optimizations that Web servers perform to reduce the load and increase the throughput. You can even enable Web server page compression modules (mod_gzip for Apache 1.x) and reduce the bandwidth usage usually in 5 times or more.
--
Regards, Manuel Lemos
Free ready to use OOP components written in PHP http://www.phpclasses.org/
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
