Offloaded MySQL, also known as “Shared SQL”, is an off node, on LAN, dedicated MySQL server customers can purchase an account on.
The service can benefit all sites, projects, etc, of any size. Your VPS will have more CPU, RAM, & disk IO available to it as you're not hosting your own SQL. On OpenVZ, this means you save 100MB+ of memory.
There is also the extra benefit of not having to worry about administering & tuning your SQL. Second only to Java, MySQL CPU/IO account for the vast majority of our resource abuse tickets.
The service costs $1.00 per month, per location.
You may purchase the service here.
Our SQL services have a 99.9% uptime guarantee.
This SLA does not apply to customers using the service outside of our network as the public IP's do get nullrouted due to attacks at times.
Our Offloaded MySQL product is available in all of our datacenters.
You may connect to it with one of the following IP addresses:
|IP Address||IP Type||Location|
|22.214.171.124||External||Las Vegas, Nevada|
|126.96.36.199||External / DDoS Protected||Las Vegas, Nevada|
|172.16.0.51||Internal||All Locations (points to local deployment)|
While connecting to the service from within BuyVM, you'll want to use the internal IP address as this will not charge against your bandwidth allocation.
All Offloaded SQL servers consist of the following as a minimum:
|Mmmmmm that's good SQL|
|Intel XEON E3 1230|
|32GB DDR3 RAM|
|4 x 1.5TB 7200RPM|
|64GB of SSD based read caching|
|Scientific Linux 6.x 64bit|
We use the MariaDB based MySQL 5.5 fork for all of our MySQL deployments.
All InnoDB tables are stored in their own files.
Support for Sphinx is also included for those that wish to use it. You'll need to run your own sphinx servers, but you can have it automatically plugged in against our SQL via the SPHINX backend plugin.
We keep a rotating 7 day, full backup, snapshot of our SQL servers.
Backups are taken at 4:00 AM using innobackupex. While we do pass the
–no-lock option, we do recommend you use InnoDB for your database storage to allow easier backups.
There is no set limit for either but the general rule of thumb is “don't be a jerk”.
We ask that you take steps to make sure you have proper indexes in place to stop table scans as these can cause extremely high CPU usage.
We do reserve the right to suspend an account when an unreasonable amount of queries are being executed.
Remember, it is a shared resource and be considerate of your neighbours. If you're concerned your site might be too busy or too big for the service, just log a ticket with support and we'll let you know.
Yes, but remember, “don't be a jerk”.
This service is made available for local users, not for an outside server to be pushing 40 mbit/sec to/from the service from across the country.
We reserve the right to nullroute any source IP that is found to be abusing the service.