# System Slowing down over a period

**URL:** <https://forum.inductiveautomation.com/t/system-slowing-down-over-a-period/35238>\
**Category:** General Discussion\
**Created:** [June 2, 2020, 5:50am UTC](https://forum.inductiveautomation.com/t/system-slowing-down-over-a-period/35238 "2020-06-02T05:50:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashwin.m](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@ashwin.m](https://forum.inductiveautomation.com/u/ashwin.m)\
**Post date:** [June 2, 2020, 5:50am UTC](https://forum.inductiveautomation.com/t/system-slowing-down-over-a-period/35238/1 "2020-06-02T05:50:51Z")

</div>

Hi,  
I am facing a sever system lag, when i open Ignition,MS SQL and other supporting software’s of the PLC.  
When i check the Task Manager, 'Zulu Platform \*64 Architecture ’ occupies most of the CPU.  
Is there a way i can optimize the usage?  
Even ignition service restart does not help sometimes.

---

<div class="post-metadata">

**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:** [June 2, 2020, 12:33pm UTC](https://forum.inductiveautomation.com/t/system-slowing-down-over-a-period/35238/2 "2020-06-02T12:33:40Z")

</div>

Sounds like overcommitted RAM yielding thrashing. Too many pieces on the same underpowered hardware, usually. Check your memory allocation in ignition.conf. If it doesn’t leave any physical ram for the other services, your system will go into swap, with terrible results. If you lower that setting, and there then isn’t enough RAM for Ignition’s workload, Ignition will choke. In that case, you need more hardware.

Personally, I never place the database in the same server as Ignition. Separate VMs in a hypervisor, perhaps, if the hypervisor is not overcommitted.

---

<div class="post-metadata">

**Author:** ![ashwin.m](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@ashwin.m](https://forum.inductiveautomation.com/u/ashwin.m)\
**Post date:** [June 4, 2020, 5:11am UTC](https://forum.inductiveautomation.com/t/system-slowing-down-over-a-period/35238/3 "2020-06-04T05:11:37Z")

</div>

I have 16 GB ram of which i have allocated 5 GB to ignition in **ignition.conf**. Still i face issues at times.  
May be i need to try out keeping the database in a VM or a different PC.

Thank you for the support

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [June 4, 2020, 11:37am UTC](https://forum.inductiveautomation.com/t/system-slowing-down-over-a-period/35238/4 "2020-06-04T11:37:41Z")

</div>

+1 on what Phil said. The database should be on a separate host.

In the meantime, check the memory allocation to SQL server. and set it to something reasonable. By default, it will use all the memory it can. This article can give some handy calculations.

> **[Understanding the Importance of Memory Setting in SQL Server](https://codingsight.com/understanding-the-importance-of-memory-setting-in-sql-server/)**
>
> The article covers the various reasons behind the performance bottlenecks caused by not setting the max memory.