暂无图片
如何在不重启MYSQL情况下,让MYSQL 释放共享内存呢?
我来答
分享
暂无图片 匿名用户
如何在不重启MYSQL情况下,让MYSQL 释放共享内存呢?

MYSQL 采用默认RPM安装,以及默认参数下, INNODB BUF SIZE 也是默认。现在MYSQL 内存占用太多

我来答
添加附件
收藏
分享
问题补充
4条回答
默认
最新
mysql> select event_name,current_alloc from sys.memory_global_by_current_bytes limit 10; +---------------------------------------------------------------------------+---------------+ | event_name | current_alloc | +---------------------------------------------------------------------------+---------------+ | memory/innodb/buf_buf_pool | 4.08 GiB | | memory/performance_schema/events_statements_history.digest_text | 2.44 GiB | | memory/performance_schema/events_statements_history.sql_text | 2.44 GiB | | memory/performance_schema/events_statements_history | 355.47 MiB | | memory/innodb/hash0hash | 114.83 MiB | | memory/performance_schema/events_statements_history_long.sql_text | 97.66 MiB | | memory/performance_schema/events_statements_summary_by_digest.digest_text | 97.66 MiB | | memory/performance_schema/events_statements_history_long.digest_text | 97.66 MiB | | memory/sql/TABLE | 73.76 MiB | | memory/performance_schema/events_statements_summary_by_digest | 39.67 MiB | +---------------------------------------------------------------------------+---------------+ 10 rows in set (0.01 sec) 如何释放performance_schema内存 不重启情况下?
暂无图片 评论
暂无图片 有用 0
mysql> select event_name,current_alloc from sys.memory_global_by_current_bytes limit 10; +---------------------------------------------------------------------------+---------------+ | event_name | current_alloc | +---------------------------------------------------------------------------+---------------+ | memory/innodb/buf_buf_pool | 4.08 GiB | | memory/performance_schema/events_statements_history.digest_text | 2.44 GiB | | memory/performance_schema/events_statements_history.sql_text | 2.44 GiB | | memory/performance_schema/events_statements_history | 355.47 MiB | | memory/innodb/hash0hash | 114.83 MiB | | memory/performance_schema/events_statements_history_long.sql_text | 97.66 MiB | | memory/performance_schema/events_statements_summary_by_digest.digest_text | 97.66 MiB | | memory/performance_schema/events_statements_history_long.digest_text | 97.66 MiB | | memory/sql/TABLE | 73.76 MiB | | memory/performance_schema/events_statements_summary_by_digest | 39.67 MiB | +---------------------------------------------------------------------------+---------------+ 10 rows in set (0.01 sec)
暂无图片 评论
暂无图片 有用 0
mysql> select event_name,current_alloc from sys.memory_global_by_current_bytes limit 10;
 +---------------------------------------------------------------------------+---------------+ | event_name | current_alloc | +---------------------------------------------------------------------------+---------------+ | memory/innodb/buf_buf_pool | 4.08 GiB | | memory/performance_schema/events_statements_history.digest_text | 2.44 GiB | | memory/performance_schema/events_statements_history.sql_text | 2.44 GiB | | memory/performance_schema/events_statements_history | 355.47 MiB | | memory/innodb/hash0hash | 114.83 MiB | | memory/performance_schema/events_statements_history_long.sql_text | 97.66 MiB | | memory/performance_schema/events_statements_summary_by_digest.digest_text | 97.66 MiB | | memory/performance_schema/events_statements_history_long.digest_text | 97.66 MiB | | memory/sql/TABLE | 73.76 MiB | | memory/performance_schema/events_statements_summary_by_digest | 39.67 MiB | +---------------------------------------------------------------------------+---------------+ 10 rows in set (0.01 sec)
暂无图片 评论
暂无图片 有用 0
张sir

这个好像没辙,只能重启解决,另外如果你的服务器内存比较小,buffer pool不要设置太大,50%的os内存就可以。

暂无图片 评论
暂无图片 有用 0
2022-10-31
有内存限制的参数没?
张sir
答主
2022-11-01
innodb_buffer_pool_size ====>设置innodb buffer pool的大小。另外你这个events_statements_history表占用的内存比较大,可以设置performance_schema_events_statements_history_long_size较小的值,控制表events_statements_history_long 的行数
回答交流
提交
问题信息
请登录之后查看
邀请回答
暂无人订阅该标签,敬请期待~~
暂无图片墨值悬赏