On Tue, May 20, 2008 at 11:54 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: > > > On May 20, 4:33 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > >> each, 100,000 requests/day is not that many. That's 4166/hour or >> 70/minute. Any non-anemic server can do that in its sleep. Our >> server has two sites each doing more than that several times a day, >> plus three smaller sites. > > when you take in peak times though, its really 200/minute during some > hours and 10-30/min on others. (at least for US only targeteed sites) > > most sites do have unrealistic expectations -- but this one is tied to > an online and offline marketing campaign. so i'm trying to be > prepared.
Well, for a Pylons site with Postgres that wants to be scalable up front, a three-server setup makes sense. One for the Pylons app, one for the static content, and one for the database. By putting them on three servers, you've already proven they can be split up. Then you can add a second server to any of the trio when it starts approaching capacity. A second static server is of course easy. A second Pylons server means you have to write the app carefully; e.g., store state data in cookies, cookie-based sessions, or the database, not on the local filesystem. A second database server is usually the hardest part; you'd need a database engine that propagates changes from any server to all the others (I think it's called replication). Or designate one server the master, but then again it's a single point of failure. If you have some tables that are mostly-read and others that are highly interactive but there's no relations between the two, you can put them in different databases on different servers with different master/slave and replication policies. This all shows the advantage of having the database on its own server in the first place; you can avoid the replication problem as long as possible. The problem with static files is that often they have to be password protected and only given to certain people (and their usage logged for statistics). That rules out using a static server for them unless your auth/logging system is in the webserver rather than in Pylons. And those systems are usually specific to the webserver, which then makes it harder to switch webservers. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
