DISQUS

Dave · 3 years ago

Another thing to consider is that if you\'re using a shared server with your webhost (most smaller sites are doing this - but I don\'t know your exact situation), the server outage/problems could just as easily have been caused by any of the other sites you\'re sharing the server with. Even if they weren\'t this time around, it\'s something to keep in mind.

In addition to caching (and if you\'re using a CMS system - there may also be cache modules that you might want to play with too) you may, eventually, want to look at a dedicated webserver. It would be more expensive, but I have a friend who is using a dedicated webhost, single server for a very popular cooking site (cookingforengineers) and he\'s handled the digg effect just fine with the single server.

It\'s also probably a good idea to doublecheck on what kind of bandwidth overages you might be liable for (if it comes to that) too. This may not apply to you, but you could be in for a rude end-of-month bill if you find that your bandwidth exceeded your monthly allocation and you\'re forced to pay for the extra bandwidth at fairly high prenegotiated rate.

webomatica · 3 years ago

hmm, yeah, I still have no idea exactly what caused the funky stuff this morning. I am considering setting up a WordPress cache plug in for now.

The dedicated server thing seems like a good idea eventually, but right now I am keeping my fingers crossed... If I were starting my own web business where it was critical the site was up all the time, I woudl do otherwise though :)

Lastly, as for the overages I should look into that. The account bandwidth is *unlimited* but who knows what that means in the fine print.