# Slowed down server

**URL:** <https://forum.inductiveautomation.com/t/slowed-down-server/19602>\
**Category:** Ignition\
**Created:** [September 10, 2018, 8:34am UTC](https://forum.inductiveautomation.com/t/slowed-down-server/19602 "2018-09-10T08:34:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [September 11, 2018, 12:31pm UTC](https://forum.inductiveautomation.com/t/slowed-down-server/19602/4 "2018-09-11T12:31:00Z")

</div>

> [@StefanGronberg](#):
>
> When using gateway scripts, am i correct to assume that i dont really have to dispose objects and variables on my own, since java should GC is when needed?

No, you don't have to dispose of objects. However, you must take care that stale versions of your jython objects don't get stuck in memory by references elsewhere. See this comment for some general advice:

> [@Some Project Resources not publishing](http://forum.inductiveautomation.com/t/some-project-resources-not-publishing/16888/3):
>
> This may be a side-effect of the fact that Ignition doesn’t/can’t track the usage and retention of python code objects throughout the gateway. This means that when your script modules have interlocking dependencies, updating one script won’t impact the code objects that other scripts have imported. You may need to make a trivial change in all of your scripts and save them all together to get it to “take”. You may also need to disable then re-enable the entire project. Consider renaming the o…

> [@StefanGronberg](#):
>
> Also, i was thinking to change init memory to 512mb ram and max to 2048, but do not think this will change anything since they allow the server to have 8GB ram and ignition uses just below 900 MB.

In my experience, Ignition settles to lower RAM usage with G1GC than with the CMS default. But wherever it settles (peak of the sawtooth in a usage trend) should be encompassed by your initmemory. I'm not sure there's ever value in having init memory != max memory -- just let Ignition grab the memory you want it have up front and keep it out of the grubby hands of competing processes.

---

_[View the full topic](https://forum.inductiveautomation.com/t/slowed-down-server/19602)._
