Over half a gigabyte; more than twice what MySQL itself is using. So, that raises an interesting question. How much memory would you say your server’s MySQL Enterprise Monitor agent uses? No bashing allowed, tell the truth. And please post if your agent runs in a small amount of memory, too.

Another thing I’m interested in: what factors contribute to the high memory usage? Under what conditions does it use a lot or a little? What can you expect, generally speaking?

On another note, I think it’s almost unfair not to mention the competition, so I will: I was playing with MONyog 2.6 recently and it started to use a lot of CPU. I think it might be architecture-specific (amd64 Ubuntu) but I can’t be sure. It was using 170% CPU on my dual-core system to monitor 2 instances.

Related posts:

1. Is agent-based or agentless monitoring best?
2. MySQL Table Sync vs. SQLyog Job Agent
3. Version 1.5.1 of the innotop MySQL monitor released
4. mk-query-digest uses less memory
5. Version 1.5.2 of the innotop MySQL monitor released