[00:00] On a standard ignition install, the gateway memory is allocated a fixed maximum amount of space from the servers ram to store and process data. We can view exactly how much that is by navigating to the diagnostics tab and then clicking on performance. Here in this status section, we'll get live data for how much memory is being used out of a total maximum amount listed in megabytes. If this number is consistently reaching the maximum expect performance degradation as the gateway is forced to free up space. Assuming that your server's architecture allows for more space, we can change this maximum amount. We can navigate to the ignition installation directory to make this configuration. Below this lesson, I've included a link to the user manual, showing the path to this directory for each operating system. Once here, you would then drill into the data folder and then open this ignition configuration file. Scroll down to the section called wrapper Java properties and look for the property called maximum java heap size.

[01:07] The line below it called wrapper java max memory is the line we're going to update. This is set to about a gigabyte of space, but we can increase this to something like four gigs or 4,000 megabytes. I'll do 4096 to be exact as this value is better as a multiple of eight. After saving the file, we can see this change take effect by restarting the gateway. So I'll go ahead and restart it now and we'll wait for it to come back up. If you're not certain how to restart the gateway, the previous lesson in this course for resetting your gateway's password does show how to restart the gateway using the gateway command utility. Once the gateway is back up, we'll log in. If we go to that performance section now, we'll see that the max memory amount increased to four gigabytes.