Bug #12810 InnoDB buffer pool status information

• Submitted: 25 Aug 2005 16:34
• Modified: 15 Oct 2012 14:57
• Reporter: Darryl Rodden
• Status: Closed
• Category: MySQL Server: InnoDB storage engine
• Severity: S4 (Feature request)
• Version: 4.1
• OS: Any (all)
• Assigned to: Jimmy Yang
• CPU Architecture: Any

[25 Aug 2005 16:34] Darryl Rodden

Description:
Would it possible to add more detailed status information about the InnoDB buffer pool to help diagnose server performance issues?  Some things that might be helpful:

a) statistics on low-memory pruning, average TTL (etc) that might indicate thrashing in the buffer pool.

b) detailed information about what is in the pool: indexes and data from which tables, how much space each is taking up.

I'm sure there are other things along these lines that would help.

thanks,
Darryl

How to repeat:
n/a

Suggested fix:
see description.

[25 Aug 2005 17:00] Heikki Tuuri

Darryn,

what is TTL?

Regards,

Heikki

[25 Aug 2005 17:40] Darryl Rodden

TTL is the Time To Live.  Sorry, I've been working with DNS so much lately that an acronym bled over into my request.

What I was trying to ask for is the average life span of entries that are pruned out of the buffer pool to make room for new ones.  Where I thought this would be useful is when all buffers in the pool are in use.  All buffers in use is not necessarily a bad thing...unless entries are being pruned at very high rates resulting in very short life spans in the buffer pool (what I call thrashing).

I hope that clarifies.

Thanks,
Darryl

[22 Dec 2010 21:30] Bugs System

Pushed into mysql-trunk 5.6.1 (revid:[e-mail]-20101222212842-y0t3ibtd32wd9qaw) (version source revid:[e-mail]-20101222212842-y0t3ibtd32wd9qaw) (merge vers: 5.6.1) (pib:24)

[15 Oct 2012 14:57] Erlend Dahl

Implemented in 5.6.2