# Gateway performance tags

**URL:** <https://forum.inductiveautomation.com/t/gateway-performance-tags/32764>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [March 3, 2020, 2:31pm UTC](https://forum.inductiveautomation.com/t/gateway-performance-tags/32764 "2020-03-03T14:31:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![indenkleefj](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/indenkleefj/32/10961_2.png) [@indenkleefj](https://forum.inductiveautomation.com/u/indenkleefj)\
**Post date:** [March 3, 2020, 2:31pm UTC](https://forum.inductiveautomation.com/t/gateway-performance-tags/32764/1 "2020-03-03T14:31:26Z")

</div>

Hi,

Currently I’m using the following tag’s to display gateway information:

- [System]Gateway/Performance/Memory Utilization
- [System]Gateway/Performance/Disk Utilization
- [System]Gateway/Performance/CPU Usage
- [System]Gateway/Performance/Available Disk Space (MB)

But when I compare these values with the task manager (server) values they are different.

Can someone explain a bit more than in the manual what the values of these tags mean?

Here is an example of the different values at the exact same moment;

Tag values:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/749bc6f2ded069f332728f258b2cca05a5d42784.png)  
Server values:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/736358bd3d55dffaf9473ba72ab7ab290f69c1cd.png)

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [March 3, 2020, 3:11pm UTC](https://forum.inductiveautomation.com/t/gateway-performance-tags/32764/2 "2020-03-03T15:11:50Z")

</div>

I’m not so sure on the CPU or Disk usage, but it might be something similar or could be a bit of lag between tag updates and task manager somewhere.

As for memory, If I recall correctly, Java doesn’t always release the memory back to the OS once it is done using it. The application is likely using less than Java is reporting via task manager, since java will hold on to space in case it is needed again.