Bug #81192 | InnoDB doesn't allocate memory for the entire buffer pool at server startup | ||
---|---|---|---|
Submitted: | 25 Apr 2016 11:22 | Modified: | 26 Apr 2016 13:38 |
Reporter: | Charly Batista | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.7 | OS: | CentOS |
Assigned to: | CPU Architecture: | Any |
[25 Apr 2016 11:22]
Charly Batista
[25 Apr 2016 11:25]
Charly Batista
Tested on CentOS 6.7 64b using MySQL 5.7.11
[26 Apr 2016 13:38]
MySQL Verification Team
Hi, This is not a bug. First and first of all, if you assign a very large InnoDB buffer pool, it will automatically be split into several smaller pools. That happened when I allocated 200 Gb of memory, for one benchmarks. However, this is not important. What you report is NOT a bug for the very simple reason. UNIX systems do NOT allocate memory until it is accessed. When process in UNIX allocates some memory, UNIX only reserves it. It does not allocate it until it is accessed. This is one of the basic concepts of every UNIX system.