I recently, blindly, updated to Percona 5.6 via the repos. I’m not running a very sophisticated database (it’s a small user group (<10) mostly for displaying timed data that can be inputed via an php interface). I have a few databases with the average size of less than a MB, the most users that are ever connected at the same time is about 5.
My server is a dedicated VSS with 1GB of ram. Percona 5.5 would use around 200-300MB of ram total when running.
However, after updating to Percona 5.6, when the server starts it instantly uses about 450MB of Physical memory and 1.5GB of virtual memory. These amounts seem to be stable once the program launches.
mysql 8877 0.0 30.0 1254936 473268 pts/0 Sl 10:35 0:05 /usr/sbin/mysqld --ba
I’ve optimized all my settings and there shouldn’t be a problem: from MySQLTuner:
Maximum possible memory usage: 338.9M (22% of installed RAM)
Highest usage of available connections: 0% (1/151)
Key buffer size / total MyISAM indexes: 8.0M/45.0K
Query cache efficiency: 0.0% (0 cached / 26 selects)
Query cache prunes per day: 0
Sorts requiring temporary tables: 0% (0 temp sorts / 1 sorts)
Temporary tables created on disk: 10% (10 on disk / 97 total)
Thread cache hit rate: 94% (1 created / 18 connections)
Table cache hit rate: 62% (111 open / 178 opened)
Open file limit used: 0% (48/470K)
Table locks acquired immediately: 100% (70 immediate / 70 locks)
InnoDB data size / buffer pool: 864.0K/128.0M
using pmap i see there are a bunch of 10MB blocks of memory allocated, which makes sense, however, I see 2 huge chunks of memory allocated for reasons unknown, which I think are the problem, I cut out some of the early address because i hit the posting character limit:
it’s just anon memory allocation, which I don’t understand why it needs to allocate so much. Seems like a bug, any help would be GREATLY appreciated, I would like to get my server down to 200-300MB again.