Re: Scalable Site Architecture
| From: | Chris | Date: | Thu, 10 May 2007 03:47:06 +0000 |
| Subject: | Re: Scalable Site Architecture | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-254708@lists.php.net to get a copy of this message | ||
bruce wrote:
Hi.. In looking for what's required fo a site, I'm trying to find docs/overview/mentors to talk to/etc,... Basically, I'm considering what's required in terms of hardware/apps/functionality for each server to be able to support a site/system of ~100,000/dayDepends on your app and what you want to do. If it's 95% "pull content from the database and display it" (eg a page from an article), look at creating static html files which get regenerated when the content is edited (http://pear.php.net/packages.php?catpid=3&catname=Caching) A webserver should handle 100k hits a day of static html pretty easily. If you're doing complicated database queries with every page hit then you're going to need a lot more database servers than http servers. -- Postgresql & php tutorials http://www.designmagick.com/