1个大型Google Cloud SQL实例，2个小型Google Cloud SQL实例或1个中型+ 1个副本? [英] 1 big Google Cloud SQL instance, 2 small Google Cloud SQL instances or 1 medium + 1 replica?

问题描述

我已经开始使用Google Cloud SQL，并且需要提高IOPS和网络速度.我已经看到，这只能改善机器类型和/或改善磁盘大小.这是我的问题.就我而言，我需要迁移2个MySQL数据库(来自2个不同的项目)，我不知道哪个更好:1个具有2个数据库的大实例?每个实例中有2个小型实例与数据库?还是1个常规实例+ 1个只读副本实例?

I've started to use Google Cloud SQL and I need to improve my IOPS and network speed. I've seen that this it's only possible improving the type of machine and/or improving the size of disk. And this is my question. In my case, I need to migrate 2 MySQL databases (from 2 different projects) and I don't know what is better: 1 big instance with 2 databases? 2 small instances with the database in each instance? or 1 regular instance + 1 read replica instance?

提前谢谢！

推荐答案

答案通常是取决于".

如果您不关心数据隔离问题，则单个实例将更加高效且易于管理.

If you're not concerned with data isolation issues, a single instance would be more efficient and easier to manage.

如果在实例之间拆分数据，那么还将限制每个数据库的性能.如果您的数据集相似且处理的请求量相同，则可能不是问题.

If you split data between instances, you're also capping performance per database. This can be a non-issue if your datasets are similar and process the same amount of requests.

如果您的应用程序工作负载严重偏向读取，则只读副本可能是扩展IOPS的解决方案.

Read replicas could be a solution to scale IOPS if your application workload is heavily skewed towards reads.

此外，无论您选择哪种选项，都请考虑 HA设置.

Also, independent of which option you will choose, consider HA-setup.

这篇关于1个大型Google Cloud SQL实例，2个小型Google Cloud SQL实例或1个中型+ 1个副本?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！