# Ignition Server Memory Spike **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [August 22, 2018, 11:10am UTC](https://forum.inductiveautomation.com/t/ignition-server-memory-spike/19356 "2018-08-22T11:10:15Z")\ **Posts on this page:** 1\ **Showing post:** 5
**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:** [August 22, 2018, 1:33pm UTC](https://forum.inductiveautomation.com/t/ignition-server-memory-spike/19356/5 "2018-08-22T13:33:29Z")
Switch to G1GC. Turn on logging of garbage collector performance. Look for pause-the-world events (aka evacuation pauses) in the logs. See this post for details: > [@Gateway / Java question 7.7.2](http://forum.inductiveautomation.com/t/gateway-java-question-7-7-2/10402/2): > > It is normal for Ignition (and java in general) to cycle between low and high memory usage. In a nutshell, java will defer difficult garbage collection tasks until memory pressure makes it necessary. If there is a great deal of garbage objects when that happens, java will stall briefly while it frees memory. If you have tweaked anything else on your system, you are probably still running what is called the Concurrent-Mark-Sweep garbage collection algorithm (standard for java7). A new garbage… --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-server-memory-spike/19356)._