On 7/16/06, B10m <[EMAIL PROTECTED]> wrote:
Instead of just throwing more RAM and CPU power at it, I wondered if there are better tricks available to speed up the site. Would it help to move PostgreSQL to a different server? Maybe move some time consuming processes to a different machine? Set up load balancing? Reconfigure Apache (again ...) ?
Your problem has apparently already been solved, but consider a couple things: 1) The cost of a new machine is usually in the range of US$2000. A standard developer will cost his company US$70/hr (pay, benefits, keeping the lights on, etc). So, if it takes you 20 hours to do something that avoids buying a new machine, you would have been better off buying the machine for an extra US$600. 2) A second machine adds both capacity as well as redundancy. Now, you can handle twice the traffic and you can still handle traffic if a machine blows up. 3) A second machine gives you upgrade options. Right now, if you needed to upgrade Apache or PG or whatever, you would have to take down the site. If you had a second machine, you could continue to serve the site (and make money!) on one machine while doing upgrades on the second. Then, you switch which machine is serving the site while upgrading the first machine. In general, it is always cheaper and better to "throw hardware at it" until the next level of hardware is over US$4000, or so. Not only will it cost less, but that money is buying a good vs. a service. (Goods are always better than equivalent services because goods stick around.) Rob --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
