MySQL Bugs: #53193: Support diagnostics link takes a long time to generate

Bug #53193	Support diagnostics link takes a long time to generate
Submitted:	27 Apr 2010 11:05	Modified:	24 May 2010 12:36
Reporter:	Bogdan Kecman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S3 (Non-critical)
Version:	2.2.0.1693	OS:	Any
Assigned to:	Mark Matthews	CPU Architecture:	Any

Description:
Support diagnostics link takes a long time to generate report. This could take few minutes for a single server and much more for a server group. This report takes a lot of resources on the mem database and can interfere with the proper work of the MEM.

How to repeat:
Start diagnostic report

Suggested fix:
Warn user before running the report.
example warning:

This report collects .... data for server/group of servers/all servers and may take a long time to run. Be prepared for it to take several minutes.
The time to run this report will be proportional to the number of servers which you are collecting data for.

On a dedicated server for which you have not requested this information before you can expect a single server report to take: xxxxx seconds.
Performance can be improved by adjusting the configuration of the innodb_buffer_pool_size of the db server to which merlin is talking.

Andy Bang writes: 
In build 2.2.1.1718.

Marcos Palacios writes: 
Verified fixed in Monitor build 2.2.1.1718.

A note has been added to the 2.2.1 changelog: 

        A warning is now provided before generating the support                                                                                            
        diagnostics information to indicate the potential time delay.