Well, I signed up for the 100TB plan on GVH because, why not? I was suspended after 2 days of using the resources in my plan.
RAM
I wanted to benchmark to see how the system would handle if I actually consumed the resources, so this is what I found. I ran a script to allocate 3GB of RAM. What I found was that instantly, the system would start swapping out the RAM to the swap and the system would slow down to a halt, even though there was "free" RAM on the system. So it would be impossible for a reasonable person to be able to use the 4GB of RAM they include in the system. This leads me to believe that their systems are out of RAM and are swapping or their swappiness is set way too high for a proper VPS system.
Upload Speed
I have quite a few servers, so I was running upload tests to them to see how it would handle. One day after having my server setup I was warned about uploading at 7.2MB/s from the disk. So I cancelled the upload and said, it doesn't make much sense for you to offer 100TB if you are saying I can't use 7.2MB/s from the disk (that would only be 17TB total served from the disk).
Either way, I loaded up a tmpfs and served the files from the RAM. It wasn't long before I was capped at 160mbps (20MB/s). I could tell this because between 3-6 threads and 3 locations, the upload speed was exactly the same as my graph proved over 12 hours.
160mbps is actually more than I was expecting but it does go to show you that they aren't allowing customers to actually use 100TB.
Downloading & Load Average
Since I was warned about the disk speed, I set up a 100gb download but limited wget to 4MB/s. Prior to the download my CPU usage was around 15% of one CPU and my load average was around 0.5 from the scps through tmpfs. After starting the wget, the CPU usage of wget was around 5% but my load average and disk wait shot up greatly. The load average went from 0.5 to 1.7 just from downloading with a limit of 4MB/s. This shows me that the disks are extremely taxed.
Two hours after starting the download and getting some things setup through yum, I get my system shut off, refunded via PayPal, and sent a notice:
"It's obvious that you are just abusing the resources here and not actually use the VPS for any legitimate reason."
Apparently, downloading a file at 4MB/s is abusing the resources. But what can you expect from a $5 100TB plan.
RAM
I wanted to benchmark to see how the system would handle if I actually consumed the resources, so this is what I found. I ran a script to allocate 3GB of RAM. What I found was that instantly, the system would start swapping out the RAM to the swap and the system would slow down to a halt, even though there was "free" RAM on the system. So it would be impossible for a reasonable person to be able to use the 4GB of RAM they include in the system. This leads me to believe that their systems are out of RAM and are swapping or their swappiness is set way too high for a proper VPS system.
Upload Speed
I have quite a few servers, so I was running upload tests to them to see how it would handle. One day after having my server setup I was warned about uploading at 7.2MB/s from the disk. So I cancelled the upload and said, it doesn't make much sense for you to offer 100TB if you are saying I can't use 7.2MB/s from the disk (that would only be 17TB total served from the disk).
Either way, I loaded up a tmpfs and served the files from the RAM. It wasn't long before I was capped at 160mbps (20MB/s). I could tell this because between 3-6 threads and 3 locations, the upload speed was exactly the same as my graph proved over 12 hours.
160mbps is actually more than I was expecting but it does go to show you that they aren't allowing customers to actually use 100TB.
Downloading & Load Average
Since I was warned about the disk speed, I set up a 100gb download but limited wget to 4MB/s. Prior to the download my CPU usage was around 15% of one CPU and my load average was around 0.5 from the scps through tmpfs. After starting the wget, the CPU usage of wget was around 5% but my load average and disk wait shot up greatly. The load average went from 0.5 to 1.7 just from downloading with a limit of 4MB/s. This shows me that the disks are extremely taxed.
Two hours after starting the download and getting some things setup through yum, I get my system shut off, refunded via PayPal, and sent a notice:
"It's obvious that you are just abusing the resources here and not actually use the VPS for any legitimate reason."
Apparently, downloading a file at 4MB/s is abusing the resources. But what can you expect from a $5 100TB plan.