# CPU and RAM problems: Clock events and Garbage Collector configuration **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [November 14, 2023, 9:50am UTC](https://forum.inductiveautomation.com/t/cpu-and-ram-problems-clock-events-and-garbage-collector-configuration/81850 "2023-11-14T09:50:13Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 14, 2023, 4:24pm UTC](https://forum.inductiveautomation.com/t/cpu-and-ram-problems-clock-events-and-garbage-collector-configuration/81850/8 "2023-11-14T16:24:36Z")
Vision is generally a light load on a gateway, for most tasks, since all of its user-interface bindings and scripts run on the client machine, not in the gateway itself. Vision gateway load is almost entirely due to tag binding delivery and running DB queries on behalf of the Vision clients. (Charting workloads, especially.) Which means you should be carefully investigating all of your gateway scripting. Look especially at (mis-)uses of `system.util.invokeAsynchronous` and `system.util.getGlobals` as likely sources of memory leaks. > [@Miguel\_Cimildoro](#): > > Ignition is running on both Windows and Linux virtual machines. IA generally recommends **against** the use of virtual machines in production when IA native drivers are involved, as hypervisors are notorious about stealing Ignition's idle CPU time to burn on other vCPUs. You have to configure your hypervisor to not do this. (No CPU overcommit on the entire physical hypervisor running your Ignition VMs, at the very least.) --- _[View the full topic](https://forum.inductiveautomation.com/t/cpu-and-ram-problems-clock-events-and-garbage-collector-configuration/81850)._