So imagine if you’re webmaster of a corporate website & you’re going public and you know for a fact that people will be interested in your IPOs, you should be expecting concurrent/simultaneous visits from 100s or 1000s of unique visitors. So if you’re on a shared hosting plan dude/dudette you’re in a lot of trouble. Shared Hosting is where you’re sharing a hosting space with other users, so when your website starts occupying resources more than its supposed to, in order to cater to the increased influx of users. Your site will be shut down! Yeahits simple plain like that, because it’s not fair to the users on the shared hosting plan with you. So how do you fix this? Well there are two ways which will I will try to explain below.If you recall, I said earlier that the problem you face with shared hosting is that when you have 1000s of visitors visiting your sites at once, it starts consuming resources on the server& it begins to encroach. So the problem is themassive influx of concurrent requests and its handling..Below are the two ways you can address this situation
Now how does that wizardry works? Well what you basically do is create a static copy of the pages on your site. When a visitor visits a site, the server loads that page & its contents every single time. This process of parsing the pages takes a lot of resources, you can reduce this process by serving static copies of your site to the users. So that static copy is readily available for every single user who visits the site. This way the server resources are not consumed for parsing a website page from the beginning.
You use WGET to pull down a static copy of your website for replacing dynamic page withstatic copy of the page – this only works if you can afford to not have your dynamic content function
The above technique is one way of making your site cope with high influx of traffic. But there is a catch and that is the dynamic functions on your site won’t be working. So yeah that is a real bummer.
If you are expecting a lot of traffic then shared hosting isn’t the hosting plan you should be buying. Either get a VPS or Dedicated Hosting. Usually you get high volume of traffic when you’ve some important event coming and important even means $$$ so it’s worth it if you spend a couple to keep your website afloat & you want to avoid any embarrassing situation.
If you have very little time & you want to avoid the hassle of setting up a self-maintained VPS & learn all the SUDO ropes. Just call your current hosting provider and tell them you need to upgrade your plan to dedicated hosting. Just in case the surge is traffic isn’t permanent then you should just subscribe for a month & then go back to shared hosting. I am sure you will find a hosting provider that will let you do something like this. Because the dedicated hosting services are very expensive. But in case you’ve time on your hands and you want to setup a self-maintained VPS then google is your best friend. Although the most sought after VPS services like Digital Ocean &Linode provide very detailed tutorials so anyone with half a brain can work their way around it BUT the keyword here is half a brain that some people lack. So in that case you go with a dedicated hosting. Just in case you happen to be someone with half a brain & is willing to go on this quest of self learning how to VPS, then go for Digital Ocean, its like the best that’s out there.thenIf you’re short on time, I wouldn’t recommend moving to something like cloud – you’re not going to be horizontally scaling much as far as know (but I’ve almost no experience on that – I might be wrong). You’d also potentially have to go through changing DNS and changing hosts – which can be a traumatic experience depending on support teams on both sides. See if godaddy can you up to a dedicated server – this would provide you dedicated CPU time and ram and get you out of an environment where you’re potentially going to be shut off for affecting other users. You might only be on this plan for a month or two – then you can make a decision if moving back to shared hosting is right for you.
If you have time to move a copy of your site to a dedicated server before re-pointing the DNS, you should see if you can benchmark that copy of your site before it goes live to see if you need further optimization or if throwing cash at it was enough. You can with something like apache ab if you have access to a linux machine (or can grab a cheap linuxvps)
As to other optimizations, SQL server is probably faster than access, and could probably be setup on your dedicated machine or a VPS. You’ll want to get the site developers involved and see if they can implement any caching or if they can make any database optimizations, as those will lower the time it takes to render a page and move onto the next visitor.