New, Lower Pricing means more resources for you!

We want to be the best performing and cost effective host in Canada for VPS and web hosting.

As of today, all plans have been adjusted to include more RAM as standard.

Nano VPS

Goes from 128MB to 512MB

Micro VPS

Goes from 256MB of RAM to 1GB

Small VPS

Goes from 512MB of RAM to 1GB ! (This is huge), we upped the port speed from 10mbit to 100mbit as well.

Medium VPS

Goes from 1GB of RAM to 2GB. We also increased the port speed to 250mbit from 100mbit.

Large and Extra Large

Get Double what they had before


Read More

We’ve done it again! More resources at no additional cost

We’ve been busy provisioning new nodes and more SSD storage. While we were at it, we noticed that we wanted to give more RAM to our clients. When it came down to discussing pricing, we all concluded on the same thoughts. Free!

As of today, all existing clients will already notice the new resources on their server(s)!

Micro VPS

Goes from 128MB of RAM to 256MB

Small VPS

Goes from 128MB of RAM to 512MB ! (This is huge), we upped the port speed from 10mbit to 100mbit as well.

Medium VPS

Goes from 512MB of RAM to 1GB. We also increased the port speed to 250mbit from 100mbit.

Introducing the Nano VPS

While we were at it, we wanted to create a plan that’s perfect for developers to get started on our platform. We’ve introduced the new Nano VPS plan with 3GB of storage, 10GB of monthly bandwidth transfer and 128MB of ram (with 128MB vSwap). All for $15 /year! Our cheapest plan yet!

Read More

vSWAP Replaces User Beancounters

Since the release of CentOS 6, OpenVZ has modified the memory management model, replacing User Beancounters. This new method is called vSWAP and is what we will be offering to all new customers as a new standard.

It eliminates a lot of confusion between Guaranteed/Burstable memory models in the old system, and allows your VPS to behave in a more predictable way (more like a dedicated server).

Most of our customers have been migrated to the newer CentOS 6 nodes and vSWAP has already been implemented. If you have been migrated, the guaranteed RAM is what you will now see in your SolusVM interface and the burstable RAM will now show as SWAP within your VPS.

You can view how much SWAP you have allocated by typing the command:

# free -m

This is the official description for vSWAP provided by the OpenVZ Wiki:

New RHEL6-based OpenVZ kernel has a new memory management model, which supersedes User beancounters. It is called VSwap.

Now you can set two primary parameters: physpages and swappages, while all the other beancounters become secondary and optional.

  • physpages
This parameter limits the physical memory (RAM) available to processes inside a container.
The barrier is ignored and should be set to 0, and the limit sets the limit.
Currently (as of >= 042stab042) the user memory, the kernel memory and the page cache are accounted into physpages.
  • swappages
This parameter limits the amount of swap space which can be used for processes inside a container.
The barrier is ignored and should be set to 0, and the limit sets the limit.

The sum of physpages.limit and swappages.limit limits the maximum amount of allocated memory which can be used by a container. When physpages limit is reached, memory pages belonging to the container are pushed out to so called virtual swap (vswap). The difference between normal swap and vswap is that with vswap no actual disk I/O usually occurs. Instead, a container is artificially slowed down, to emulate the effect of the real swapping. Actual swap out occurs only if there is a global memory shortage on the system.

As always, if you have any questions regarding this post, please contact us or post a comment below.

Read More

What is the Difference Between “Guaranteed” and “Burstable” RAM on OpenVZ?

Another popular question we get at is: “What is the difference between Guaranteed and Burstable RAM.”

To answer this question we must first briefly understand how OpenVZ works. Unlike other virtualization methods (XEN, VMWare) OpenVZ does not “Guarantee” system resources. Think of it more like a “chroot” of sorts. While it is not exactly the same as the chroot definition, it acts similarly to those principles. As a result the Virtualized Environments (VE’s) will share the Harware Node’s Kernel, RAM and SWAP space. From there, OpenVZ sets limits to each individual VE for such things as CPU speed and time, hard drive quota, hostname, IP addresses and more.

All of these limits are viewable in the following file on a OpenVZ based VE: /proc/user_beancounters

So how does all of this information relate to the amount of RAM on my VPS??

The important number is the Burstable amount. The reason for this is because the majority of programs allocate memory for more than what they actually use. Usually this is about double.

Lets take YUM for example. In order to run it, almost 100mb of RAM will get allocated, but it will only use about half that (there are variables here depending on what it’s actually doing). Majority of programs do this just incase they need more.

Example: If the “Small” package on were to have 128mb burst and guaranteed RAM, running #yum update -y would lead to an error. This is because the yum program will try to allocate about 100mb of RAM. OpenVZ will see that this is higher than the burstable limit (assuming there are other things running as well), resulting in the error.

Since the “Small” VPS package has a burstable amount of 256mb it allows YUM to excecute perfectly. The actual RAM usage is under the guaranteed 128mb and the allocated is under 256mb.


The Guaranteed RAM is the amount the can be used, the Burstable RAM is the amount that can be allocated. Generally assume that the program will allocate double the RAM it uses.

Recommendations When Buying

In general, build up a good relationship with your host and make sure they are honest with you. There is nothing wrong with asking for the full spec of the hardware node and asking how many customers are on it or how much of it’s resources are allocated (or intend to be allocated).

From there it’s important to know just how much ram your system will be using. Always get double the amount of burstable ram to ensure that your programs will run perfectly. If you know your system will be using 512mb of ram, make sure that you get a burstable amount of 1gb or more. Always look at the burstable limit as a rule of thumb.

In the end, it’s your money and you need to make sure that it’s being well invested.

Read More