# Wisdom from performance testing Ignition

**URL:** <https://forum.inductiveautomation.com/t/wisdom-from-performance-testing-ignition/114769>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 30, 2026, 3:00pm UTC](https://forum.inductiveautomation.com/t/wisdom-from-performance-testing-ignition/114769 "2026-03-30T15:00:41Z")\
**Posts on this page:** 1\
**Showing post:** 15

<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:** [March 31, 2026, 6:04am UTC](https://forum.inductiveautomation.com/t/wisdom-from-performance-testing-ignition/114769/15 "2026-03-31T06:04:49Z")

</div>

> [@kayla.hebert](#):
>
> how to measure performance

In jython, use java's `System.nanoTime()` call to obtain cross-CPU synchronized clock nanoseconds. This call is specifically designed for performance tracking.

In Ignition's expression language, consider using my Integration Toolkit's `nanoTime()` and/or `timeMe()` expression functions.

---

_[View the full topic](https://forum.inductiveautomation.com/t/wisdom-from-performance-testing-ignition/114769)._