blocks|key|803943|text|预先警告:我对Amazon一无所知，所以这个答案可能是毫无意义的。我是从一般的MySQL角度回答的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|803944|嗯，您的设置并不完全是最优的，但是有一些方法可以对其进行优化。您希望防止频繁地打开/关闭表，因此您希望同时打开许多表。|803945|为此，请执行以下操作：|803946|确保操作系统允许MySQL拥有大量打开的文件|unordered-list-item|803947|正确设置缓存|offset|length|803948|您可以在MySQL手册中找到更多的参考资料。|803949|实际需要多高的限制取决于资源的限制。每一张打开的桌子都需要内存--我不知道要多少钱。像调谐底漆或mysqltuner.pl这样的脚本可以帮助您防止内存过多。|803950|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_table_cache|1|http://dev.mysql.com/doc/refman/5.0/en/table-cache.html|2|http://www.day32.com/MySQL/|3|http://mysqltuner.pl/mysqltuner.pl^0|0|0|0|0|4|2|0|0|4|7|1|0|17|4|2|1C|D|3|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|17|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|18|8|@]|9|@$K|19|L|1A|1|1B]]|A|$]]|$1|M|3|N|5|6|7|1C|8|@]|9|@$K|1D|L|1E|1|1F]]|A|$]]|$1|O|3|P|5|6|7|1G|8|@]|9|@$K|1H|L|1I|1|1J]|$K|1K|L|1L|1|1M]]|A|$]]|$1|Q|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]|10|$5|T|U|V|A|$W|11]]|12|$5|T|U|V|A|$W|13]]]]

Warning in advance: I have no clue about Amazon RDS, so this answer may be absolute nonsense. I am answering from a generic MySQL perspective.

Well, your setup is not entirely optimal, but there are some ways to tune it. You want to prevent opening/closing tables too often, so you want a lot of tables open at the same time.

To do this:

<ul>
<li>Make sure your OS allows MySQL to have a lot of open files</li>
<li>Set the <a href="http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_table_cache" rel="nofollow">table_cache</a> properly</li>
</ul>

You can find some more references in the <a href="http://dev.mysql.com/doc/refman/5.0/en/table-cache.html" rel="nofollow">MySQL manual</a>.

How high you actually want this limit depends on the constraints of your resources. Each open table takes memory - I'm not sure how much. A script like the <a href="http://www.day32.com/MySQL/" rel="nofollow">tuning primer</a> or <a href="http://mysqltuner.pl/mysqltuner.pl" rel="nofollow">mysqltuner.pl</a> can help you to prevent overcommitting your memory.

I have an application that stores isolated (and sharded) user data in separate MySQL schemas (aka databases) with with identical table structure (3 InnoDB tables), one for each account. We're using Amazon RDS to store the data and there are currently about 30k schemas per RDS instance. My question is about how to optimize the MySQL settings (or in terms of RDS, the Parameter Group settings) for a large number of schemas.

I know there is a reflex to condemn the practice of having thousands of identical schemas, suggesting instead that there be a single schema with something like an indexed "account_id" column. The argument generally given is that the penalty for shard-walking or schema changes outweigh the benefits. In our case, we need to keep the data isolated and there is never any interaction between different accounts.

What are some ways to maximize performance in a situation like this?

Optimization for thousands of schemas in MySQL

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个应用程序，它以相同的表结构(3个MySQL表)将孤立(和切分)的用户数据存储在单独的InnoDB模式(也称为数据库)中，每个帐户都存储一个。我们使用Amazon存储数据，目前每个RDS实例大约有30k模式。我的问题是如何为大量模式优化MySQL设置(或RDS，参数组设置)。我知道有一种条件反射来谴责拥有数千个相...

MySQL中数千种模式的优化-腾讯云开发者社区-腾讯云

问MySQL中数千种模式的优化
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL中数千种模式的优化EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL中数千种模式的优化
EN