Re: I've got 12 domains on one website server.
Posted by:
blepore
(---.rochester.res.rr.com)
Date: February 01, 2008 04:16PM
I'm a bit confused. It sounds to me like you're saying you're tired of slow speeds from your current Web host, and you found that installing Wamp on your current machine for testing is much faster and therefor you're thinking of moving from that host to running everything off your local machine? Is that what you're saying?
Testing on localhost will ALWAYS be faster. It does not go out to the internet. Judging your speed between localhost and a true Web connection is ill advisable. Additionally, you're probably only connected to the Internet using a cable modem or DSL or the like and not a business connection. If your sites are getting hammered enough that a business connection like your current host can't handle it, then doing it on your local machine is going to result in you DDOSing yourself and your clients sites.
My recommendations: Either get a second Web server and split the load, or get a much faster server. With multiple servers, you can either split the domains against the multiple servers, or you can configure the DNS to use two different IPs for the domains. With that you'll have to make sure only one is the master DB and the second replicates its data. This could be non-trivial depending on your system. Also, if you're using Etags make sure that they are not derived using the file system (something Apache does by default) because then browsers won't properly cache the files that are being served out. With this method, you need to make sure a user always uses the same path for files through out their entire stay (I assume a browser is smart enough to not go back and forth if their DNS lookup reported multiple A records, but I've never been in a position to test this so I do not know exactly).
In the mean time, I would begin looking at all of the research Yahoo has put out on high performance Web sites. Just properly configuring things like combining all CSS and JavaScript into one file for each type, setting Expires, Etags, and LastModified for your HTTP headers, and moving the placement of your JavaScript to the end (plus using DOMContentLoaded) could make your sites load faster.
Of course, I probably just misinterpreted what you were looking for and wrote all of that for nothing. If not though, I hope it helps.
If you end up needing a new server, check to see who the culprit(s) is that is getting the most traffic and try to split the cost of the upgrade with them.
Oh, and don't go with CI Host. They're based in Texas, so I understood why they were down earlier in the year when they were basically getting floods in certain areas, but I have no idea why they were down this morning... Weather.com reports their location as Sunny at the present time. And earlier this year when we were looking to upgrading, they would only offer the current OS that we were using, RedHat 7.1! We talked them into a custom package to get CentOS 4 on (5 came out like 2-4 months after our move), but it was a pill to get them to understand why we didn't want to reinstall a 6 year old OS that everyone I talked to knew how to exploit.
We moved one of our servers from CI Host to GoDaddy, and we have not experience downtime. The only draw backs I would consider with them were that the latency was a bit higher than I'd have liked, and that they restrict you to 7 or 8 IPs (a problem if you need SSL) and only allow 1000 outgoing SMTP connections a day (a problem if you have a newsletter feature).