In the world of web hosting, there are many options for how to manage the computers that run a website, and it can be difficult to figure out what might be best for you. Since enterprise websites require the full resources of a server (or multiple servers) to ensure optimal performance for the site’s users, it’s important to make sure the best hosting option is chosen. When deciding upon those options, the choice often comes down to one of two possible approaches: dedicated or virtual hosting. Should you use your own physical server dedicated solely to you, or should you use a virtual server, which uses software to emulate a physical server on a virtual host? Let’s look at the pros and cons of each option:
VMs on ESXi run Windows and Linux operating systems near flawlessly. It’s also a powerhouse for many sizeable virtual desktop deployments running on VMware View or Citrix XenDesktop. And more recently VMware was in the news because they will soon power Google’s Chrome virtual desktop cloud and provide access to Windows application. How cool is that!
The primary disadvantage to using a VPS is its lack of performance. The organization that provides the VPS will typically throttle the server's performance in an effort to maximize the number of VPSs that the physical server is able to accommodate. In the unlikely event that the VPS's performance is not throttled, it then becomes possible for an adjacent VPS to consume excessive resources, to the point of impacting the VPS's performance.

I was on a mission to look for new VPS hosting for our new website. It was between Bluehost, Dreamhost, and InMotion Hosting. After a chat with Adam, it is clear that InMotion Hosting is the best choice for us because of the outstanding support. I want to let you and your department know that Adam is doing an outstanding job for your company. I will refer my friends to you guys."
CPU is one area in which we are quite unique with VPS Hosting. We do not lock you down to a certain number of cores that you are forced to stay within, but balance it across our fleet of VPS servers. If you are using so much CPU that you are affecting other users on your server, we will either move you to another server or ask you to upgrade your plan.

Self-Managed VPS customers have to make sure everything works the way they configure them and perform updates themselves. Obviously, this is not a job for novice users. It is probably not even a job for someone who does not feel comfortable managing services and scripts themselves. If in doubt, you should probably stick with a Managed VPS product and focus, instead, on growing your business and optimizing your site.
As you can see, each of these options has its own advantages, so you will need to weigh the options and determine which one will best meet your site’s needs. Depending on the amount of traffic your site receives, the resources needed to maintain the best performance for your site’s users, or any other specifications that you might need to consider (such as high availability, disaster recovery, or load balancing), either option might be best for you. If you need help determining the ideal solution for your website, please contact us to speak to a hosting expert.
With a VPS, you receive all the power of Dedicated Server Hosting plus the ability to maintain your own set of services and customizable disk space. Here, you can also perform any desired actions from your control panel, without the need to contact our technical support team. With Shared Hosting, however, you have limited administrative access and are not able to customize software configurations. Learn more about the differences →
Our cloud provisioning system is able to rapidly deploy new servers after orders have been verified. The setup time for a VPS server actually varies depending on if you are using a Linux or Windows operating system. On Linux based servers you should see the VPS online within 15-30 minutes. For a Windows based server you will see the VPS online within 1-2 hours.
You can host a basic web application, such as a blog or simple website in a VPC, and gain the additional layers of privacy and security afforded by Amazon VPC. You can help secure the website by creating security group rules which allow the webserver to respond to inbound HTTP and SSL requests from the Internet while simultaneously prohibiting the webserver from initiating outbound connections to the Internet. You can create a VPC that supports this use case by selecting "VPC with a Single Public Subnet Only" from the Amazon VPC console wizard.
If you host it in a VPS environment, your site won't share resources with neighboring sites, the way it would with shared hosting. In fact, your site lives in a partitioned server area that has its own operating system, storage, RAM, and monthly data transfer limits, so you can expect smoother, more stable site performance. The sites with which you share your server are far less likely to affect your site—or even take it down altogether—than they would be on a shared site. Knowing how VPS setups operate is just the first step, however. You still need to familiarize yourself with the essential features needed for building a rock-solid, VPS-hosted website.
Partitioning a single server to appear as multiple servers has been increasingly common on microcomputers since the launch of VMware ESX Server in 2001. The physical server typically runs a hypervisor which is tasked with creating, releasing, and managing the resources of "guest" operating systems, or virtual machines. These guest operating systems are allocated a share of resources of the physical server, typically in a manner in which the guest is not aware of any other physical resources save for those allocated to it by the hypervisor. As a VPS runs its own copy of its operating system, customers have superuser-level access to that operating system instance, and can install almost any software that runs on the OS; however, due to the number of virtualization clients typically running on a single machine, a VPS generally has limited processor time, RAM, and disk space.[2]
×