Bug #71493 Improve visibility of expected MEM database server's disk usage
Submitted: 27 Jan 2014 11:18 Modified: 26 Feb 2014 10:15
Reporter: Simon Mudd (OCA) Email Updates:
Status: Verified Impact on me:
Category:MySQL Enterprise Monitor: Server Severity:S4 (Feature request)
Version:3.0.5 OS:Any
Assigned to: CPU Architecture:Any
Tags: windmill

[27 Jan 2014 11:18] Simon Mudd
Estimating the disk usage requirements of a MEM database server, whether running standalone or as a dedicated server can be quite hard.

It depends on various things:
- purge periods configured in global settings for normal instruments and QUAN data
- the number of servers which are being monitored
- the number of servers where QUAN is enabled and how many statements they are seeing

MEM does monitor disk usage (not sure about MEM db table sizes) so has an idea about this.

How to repeat:
see above

Suggested fix:
Provide a page where storage space used for the last N days can be determined and use this to extrapolate, using the currently configured purge settings as to what the total disk space usage is likely to be.

Provide information so that the use can identify how these numbers would change if the number of servers were to change, the activity of the QUAN monitored servers were to change or the purge periods were adjusted.

Basically provide some sort of calculator so these calculations can be done easily.
That way the DBA or system administrator can leave MEM running monitoring just a few servers to get an idea of disk usage and then use this facility to guestimate the disk requirements of a fully loaded MEM server and which PURGE periods would be most appropriate.

This prevents problems later on as more servers are added to the system.
[26 Feb 2014 10:15] MySQL Verification Team
Hello Simon,

Thank you for the feature request!