High RAM Cloud Servers
GoGrid High RAM Cloud Servers deliver a large amount of available memory in the cloud on a redundant 10-Gbps network fabric.
- Up to 256 GB RAM
- 10-Gbps public and private network
- High I/O local SSD OS drive
- Optimized for Block Storage
GoGrid offers hourly, monthly, and annual Cloud Server pricing. With our hourly pay-as-you-go option, you simply pay for the resources you use. There is no commitment, and you’re free to cancel at any time. If you’re willing to commit to a prepaid monthly or annual Cloud Server plan, you can save money when compared to hourly Cloud Server charges.
High RAM Cloud Server Sizes and Pricing by Type
|High RAM Cloud Servers||RAM||Cores||SSD Storage||Hourly||Monthly
|X-Large||16 GB||4||40 GB||$0.64||$350.40||$2,803.20|
|2X-Large||32 GB||8||40 GB||$1.02||$558.45||$4,467.60|
|4X-Large||64 GB||16||40 GB||$1.64||$897.90||$7,183.20|
|8X-Large||128 GB||28||40 GB||$2.62||$1,434.45||$11,475.60|
|16X-Large||256 GB||40||40 GB||$3.49||$1,910.78||$15,286.20|
- Your CPU allocation will vary depending on the profile of the physical node on which your Cloud Server resides.
- High RAM Cloud Servers only support Linux.
Deploy multi-data-center solutions without having to rebuild your Cloud Server. You can copy your GoGrid Server Image (MyGSI) for a one-time $50 fee. See our wiki for complete details.
Bandwidth Pricing (data transfer)
On GoGrid, data transfer is measured in gigabytes. There are no charges for private network data transfer between servers within a single data center. There are also no costs associated with inbound data transfer to your servers. You’ll only be charged based on your outbound data transfer. Pricing for outbound data transfer starts at just $0.12 per GB. See the Data Transfer page for complete details.
About Hourly Cloud Server Billing
With this option, you accrue usage charges by the hour for each Cloud Server you create. To stop all charges, you simply delete all Cloud Servers in the account. For example, if you create a 1 GB server using GoGrid and 1 hour later delete the server, you accrue charges for 1 hour of usage. Usage consists of accumulated hourly charges, transfer, and Cloud Storage charges.
About Prepaid Cloud Server Billing
If you deploy prepaid Cloud Servers, you’re billed in advance for each server. To stop all charges, you simply delete all virtual servers in the account before the end of the term. Prepaid servers are not prorated. For example, if you create a 1 GB monthly prepaid Cloud Server using GoGrid and 10 days later delete the server, you’ll still be charged for the full month. If you deploy a single server for 10 days, delete the server, and then deploy a second server for the rest of the month, you’ll be charged for two monthly prepaid Cloud Servers. Additional usage charges consist of transfer and Cloud Storage charges.
Open source products like Memcached can take advantage of the large available memory on High RAM Cloud Servers. Scale your solution horizontally by easily adding multiple High RAM Cloud Servers via the management console or API. Even if you use Memcached for internal purposes, you can still take advantage of our high-performance fabric, which is a redundant 10-Gbps public and private network.
MongoDB attempts to store the working set in memory. High RAM Cloud Servers offer a strong fit for users with large working sets that want to maximize the performance of MongoDB. There’s no special configuration required for MongoDB—it uses as much RAM as you can make available. High RAM Cloud Servers are also optimized for Block Storage so you can easily attach Block Storage volumes in a RAID 10 configuration if you require additional storage.
Riak has an option where you can configure it to function as a caching server. You can do so by using the Memory Backend storage engine that ships with Riak within the distribution. This approach requires a configuration change because Bitcask is the default engine. Using the Memory Backend transforms Riak into a caching server where it will attempt to use in-memory tables instead of persisting to disk. Riak still maintains its distributed architecture, so it’s highly resistant to failure even in this mode.
|CentOS 6.5 (64-bit)||None|
|Debian 7.5 (64-bit)||None|
|Ubuntu 14.04 LTS (64-bit)||None|
See the wiki for more details regarding supported operating systems.