GridVirt provides high performance SSD based VPS servers from $25 per month. VPS nodes are virtualized with KVM to ensure stability & GridVirt limits the number of Virtual Machine per hardware node to no more than 9 to ensure consistent CPU & IO performance. They are currently collocating in the Choopa DuPont Fabros in Piscataway, NJ, each hardware node is limited to 100 Mbps uplink but is unmetered.
| Plan | Virtualization | CPU Cores | RAM | HDD | Bandwidth | Monthly Cost |
|---|---|---|---|---|---|---|
| 1 Node | KVM | 4 | 1.5GB | 20GB | Unmetered | $25.00 |
| 2 Nodes | KVM | 4 | 3GB | 40GB | Unmetered | $50.00 |
| 3 Nodes | KVM | 4 | 4.5GB | 60GB | Unmetered | $75.00 |
| 4 Nodes | KVM | 8 | 6GB | 80GB | Unmetered | $100.00 |
| 5 Nodes | KVM | 10 | 7.5GB | 100GB | Unmetered | $125.00 |
| 6 Nodes | KVM | 12 | 9GB | 120GB | Unmetered | $150.00 |
| 7 Nodes | KVM | 14 | 10.5GB | 140GB | Unmetered | $175.00 |
| 8 Nodes | KVM | 16 | 12GB | 160GB | Unmetered | $200.00 |
| 9 Nodes | KVM | 18 | 12.5GB | 180GB | Unmetered | $225.00 |
| 10 Nodes | KVM | 20 | 15GB | 200GB | Unmetered | $250.00 |
| Coupons | Code | Added | Expires |
|---|---|---|---|
25% Off Your First MonthTake 25% off your first invoice with GridVirt with this coupon code. |
JONODE25  |
2012-09-20T02:03:55+00:00 | Never |
| Plan | Uploaded | UnixBench | I/O | IOPS | Bandwidth | Location | Report |
|---|---|---|---|---|---|---|---|
| 2 Nodes | 2012-12-27 18:03:27 UTC | 3994.5 | 610.0 MB/s | 3910 | 6.1 MB/s | Matawan, NJ, United States | Report |
| 3 Nodes | 2012-11-18 21:04:29 UTC | 3939.1 | 607.0 MB/s | 3538 | 1.2 MB/s | Matawan, NJ, United States | Report |
| 1 Node | 2012-10-24 22:45:48 UTC | 2047.0 | 1000.0 MB/s | 15156 | 22.2 MB/s | Matawan, NJ, United States | Report |
| 1 Node | 2012-10-05 07:23:59 UTC | 2211.5 | 1300.0 MB/s | 16793 | 26.9 MB/s | Matawan, NJ, United States | Report |
| 1 Node | 2012-09-23 06:16:56 UTC | 2169.3 | 1100.0 MB/s | 16389 | 28.5 MB/s | Matawan, NJ, United States | Report |
| 2 Nodes | 2012-09-01 04:30:28 UTC | 3202.5 | 912.0 MB/s | 16107 | 13.5 MB/s | Matawan, NJ, United States | Report |
| 1 Node | 2012-08-31 17:26:13 UTC | 2333.6 | 1300.0 MB/s | 13781 | 25.4 MB/s | Matawan, NJ, United States | Report |
| 1 Node | 2012-08-31 16:02:56 UTC | 2455.9 | 1400.0 MB/s | 14402 | 19.4 MB/s | Matawan, NJ, United States | Report |
| 1 Node | 2012-08-31 14:36:31 UTC | 2316.6 | 1400.0 MB/s | 15371 | 23.7 MB/s | Matawan, NJ, United States | Report |
| 1 Node | 2012-07-31 23:33:42 UTC | 3895.2 | 1300.0 MB/s | 14749 | 25.5 MB/s | Seattle, WA, United States | Report |
| 1 Node | 2012-07-31 07:27:02 UTC | 3865.8 | 1100.0 MB/s | 15587 | 29.2 MB/s | Seattle, WA, United States | Report |
| 1 Node | 2012-07-28 14:49:08 UTC | 3875.2 | 1200.0 MB/s | 14239 | 29.2 MB/s | Seattle, WA, United States | Report |
| 2 Locations |
|---|
| Seattle, WA, USA |
| Piscataway, NJ, USA |
| Whois |
|---|
| Domain Created: 6 March, 2011 |
IMPORTANT! Uptime monitoring is currently in open beta and may report incorrect data. Click here for information about how it works.
| Monitored for | Uptime (average location uptime) |
|---|---|
| 6 months | 100% |
| Downtime | When | Location down |
|---|---|---|
| 6 minutes (375 sec) | 2013-05-19 02:05:07 UTC | Piscataway, NJ, USA |
| 8 minutes (476 sec) | 2013-05-18 14:45:59 UTC | Piscataway, NJ, USA |
| about 1 hour (2790 sec) | 2013-05-18 05:20:52 UTC | Piscataway, NJ, USA |
| 4 minutes (246 sec) | 2013-05-17 21:04:26 UTC | Piscataway, NJ, USA |
| 3 minutes (177 sec) | 2013-05-17 16:20:58 UTC | Piscataway, NJ, USA |
| 3 minutes (180 sec) | 2013-05-17 16:08:42 UTC | Piscataway, NJ, USA |
| 4 minutes (234 sec) | 2013-05-17 16:00:56 UTC | Piscataway, NJ, USA |
| 12 minutes (695 sec) | 2013-05-16 17:13:11 UTC | Piscataway, NJ, USA |
| 6 minutes (330 sec) | 2013-05-04 05:16:34 UTC | Piscataway, NJ, USA |
| 8 minutes (497 sec) | 2013-05-04 04:15:28 UTC | Piscataway, NJ, USA |
| about 15 hours (54239 sec) | 2013-04-27 08:12:06 UTC | Piscataway, NJ, USA |
| 3 minutes (155 sec) | 2013-04-27 06:48:37 UTC | Piscataway, NJ, USA |
| 1 minute (60 sec) | 2013-04-22 17:34:43 UTC | Piscataway, NJ, USA |
| 5 minutes (309 sec) | 2013-04-20 07:13:10 UTC | Piscataway, NJ, USA |
| 4 minutes (261 sec) | 2013-04-20 07:03:12 UTC | Piscataway, NJ, USA |
| 6 minutes (341 sec) | 2013-04-20 05:17:58 UTC | Piscataway, NJ, USA |
| 4 minutes (210 sec) | 2013-04-20 04:09:35 UTC | Piscataway, NJ, USA |
| 1 minute (50 sec) | 2013-04-17 19:32:16 UTC | Piscataway, NJ, USA |
| 1 minute (53 sec) | 2013-04-09 17:57:00 UTC | Piscataway, NJ, USA |
| 3 minutes (197 sec) | 2013-04-09 12:24:35 UTC | Piscataway, NJ, USA |
| 3 minutes (181 sec) | 2013-04-09 12:20:26 UTC | Piscataway, NJ, USA |
| 6 minutes (367 sec) | 2013-04-06 07:10:34 UTC | Piscataway, NJ, USA |
| 2 minutes (125 sec) | 2013-04-02 19:01:16 UTC | Piscataway, NJ, USA |
| 12 minutes (693 sec) | 2013-01-22 01:59:02 UTC | Piscataway, NJ, USA |
| 7 minutes (421 sec) | 2013-01-09 09:30:21 UTC | Piscataway, NJ, USA |
| 2 minutes (103 sec) | 2012-12-27 07:34:47 UTC | Piscataway, NJ, USA |
| Monitored for | Uptime (any node up) | Nodes monitored |
|---|---|---|
| 6 months | 100% | Node 2, Node 1 |
| Downtime | When | Nodes down |
|---|---|---|
| 6 minutes (375 sec) | 2013-05-19 02:05:07 UTC | Node 1 |
| 8 minutes (476 sec) | 2013-05-18 14:45:59 UTC | Node 1 |
| about 1 hour (2790 sec) | 2013-05-18 05:20:52 UTC | Node 1 |
| 4 minutes (246 sec) | 2013-05-17 21:04:26 UTC | Node 1 |
| 3 minutes (177 sec) | 2013-05-17 16:20:58 UTC | Node 1 |
| 3 minutes (180 sec) | 2013-05-17 16:08:42 UTC | Node 1 |
| 4 minutes (234 sec) | 2013-05-17 16:00:56 UTC | Node 1 |
| 12 minutes (695 sec) | 2013-05-16 17:13:11 UTC | Node 1 |
| 6 minutes (330 sec) | 2013-05-04 05:16:34 UTC | Node 1 |
| 8 minutes (497 sec) | 2013-05-04 04:15:28 UTC | Node 1 |
| about 15 hours (54239 sec) | 2013-04-27 08:12:06 UTC | Node 1 |
| 3 minutes (155 sec) | 2013-04-27 06:48:37 UTC | Node 1 |
| 1 minute (60 sec) | 2013-04-22 17:34:43 UTC | Node 1 |
| 5 minutes (309 sec) | 2013-04-20 07:13:10 UTC | Node 1 |
| 4 minutes (261 sec) | 2013-04-20 07:03:12 UTC | Node 1 |
| 6 minutes (341 sec) | 2013-04-20 05:17:58 UTC | Node 1 |
| 4 minutes (210 sec) | 2013-04-20 04:09:35 UTC | Node 1 |
| 1 minute (50 sec) | 2013-04-17 19:32:16 UTC | Node 1 |
| 1 minute (53 sec) | 2013-04-09 17:57:00 UTC | Node 2 |
| 3 minutes (197 sec) | 2013-04-09 12:24:35 UTC | Node 2 |
| 3 minutes (181 sec) | 2013-04-09 12:20:26 UTC | Node 2 |
| 6 minutes (367 sec) | 2013-04-06 07:10:34 UTC | Node 1 |
| 2 minutes (125 sec) | 2013-04-02 19:01:16 UTC | Node 1 |
| 12 minutes (693 sec) | 2013-01-22 01:59:02 UTC | Node 2 |
| 7 minutes (421 sec) | 2013-01-09 09:30:21 UTC | Node 1 |
| 2 minutes (103 sec) | 2012-12-27 07:34:47 UTC | Node 1 |
GridVirt is one of a growing number of hosts to over SSD VPS nodes, this allows a huge increase in IO performance usually at a sacrifice of disk space (GridVirt makes up for this by having an additional SAN based HDD). They were kind enough to let us have a play with one of their High Performance Virtual Grid Servers, each of which are advertised to deliver up to 1.3GB/s IO performance. Naturally, we jumped at the chance to put this node through its paces.
The 1 Node SSD VPS will run you $25 per month, you can pay an additional $5 per month to increase your IO performance by an additional 30%.
Each nodes has:
Having a quick look at /proc/cpuinfo confirms that there's 4 allocated CPU Cores. Due to the way KVM virtualizes the core we're unable to see exactly what CPU's GridVirt uses but it's one of the Intel Xeon family.
As with every review we do we ran our own ServerBear benchmarking script on a clean install of Ubuntu 12.04 LTS, you can view the full detail of the report below.
@ServerBear on Twitter | About ServerBear | Contact Us | Privacy Policy | © 2013 ServerBear
