Bug #54304 Using QUAN, agent consumes too much RAM for big queries
Submitted: 7 Jun 2010 19:00 Modified: 9 Jan 2015 10:31
Reporter: Andrii Nikitin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version:2.2.1.1717 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[7 Jun 2010 19:00] Andrii Nikitin 
Description:
Enabled QUAN significantly increases RAM usage by agent if Proxy serves big queries.

E.g. processing single query with 55M will increase agent RAM usage more than 1G.
(without QUAN enabled RAM usage increase compatible with query size)

QuerySize  RAM Linux    RAM Mac    RAM Windows
3M         370M         100M          
8M         450M                    272M
21M        1.2G         655M       675M
55M        2G (*)       1.7G       1.2G (**)

*) - process got OOM so it was not possible to fully test result
**) - process didn't complete for 50 min for some reasons (PROCESSLIST shows "Sleep" for 3025 seconds for process). (let's assume also memory-related problem)

related to bug 40462

How to repeat:
1. Generate big queries using bash script from bug #54063
2. Increase max allowed packet for server upto 1G
3. Enable query analyzer
4. run query trough Proxy

(see also attached linux.log)

Suggested fix:
optimize memory usage
[7 Jun 2010 19:01] Andrii Nikitin 
log from linux tests

Attachment: linux.log (application/octet-stream, text), 12.27 KiB.
[7 Jun 2010 19:11] Andrii Nikitin 
related to bug 40462
[12 Aug 2010 9:01] Enterprise Tools JIRA Robot 
Michael Schuster writes: 
adjusting summary to reflect current findings (ie. quan is not necessary)
[2 Dec 2010 16:08] Enterprise Tools JIRA Robot 
Diego Medina writes: 
I used a file that was 21MB in size and the agent went all the way to 400MB.
[2 Dec 2010 16:09] Enterprise Tools JIRA Robot 
Diego Medina writes: 
tested with 2.3.1.2038