Re: Memory governor for Workbench

[Beeling Chang]

MySQL workbench is hosted on a server for shared usage. So we don't really have control over how they use the tool and how long is being used. We did observe the memory spike for some processes (each user has its own workbench process). A single workbench process can take 7-10 GB memory. If 10 users are running this tool simultaneously, the server can hit 100% memory consumption (32GB). This also cause the Windows page file grow over 100GB!!!
Eventually, the server became unresponsive and we have to reboot it. That is the reason why we want to governor memory per user/process. if they consume more with bad query, it will only run OOM for their own process and will not bring down others.
In SQL Workbench/J, we can configure (vm.heapsize.preferred = 4096) so that each process won't go over 4GB. What about MySQL Workbench?

Thanks!