[DOC] on estimating dictionary size

Bug #1267810 reported by Aurimas Mikalauskas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Invalid
Undecided
Unassigned
5.1
Won't Fix
Undecided
Unassigned
5.5
Fix Released
Medium
Hrvoje Matijakovic
5.6
Invalid
Undecided
Unassigned

Bug Description

[In:Percona Server Documentation]

The following document:

  http://www.percona.com/doc/percona-server/5.5/management/innodb_dict_size_limit.html

Suggests that we can use "Total memory allocated" (by subtracting buffer pool size from it) from ENGINE INNODB STATUS to understand how large is the dictionary size, however in one of the articles:

  http://www.mysqlperformanceblog.com/2010/05/06/how-much-memory-innodb-dictionary-can-take/

Peter suggests that:

  Dictionary Cache is not included in “Total Memory Allocated” in SHOW INNODB STATUS any more, as that allocations were moved to use malloc() and so Innodb does not track them any more.

Tags: doc

Related branches

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Moreover, I see that dictionary memory is reported separately in recent upstream MySQL (5.5.35 in this case):

...
----------------------
BUFFER POOL AND MEMORY
----------------------
Total memory allocated 74055680; in additional pool allocated 0
Dictionary memory allocated 52909
Buffer pool size 4416
...

So, this entire section on our page needs clarifications and may be redundant.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3085

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.