# Diagnosing high CPU Perspective worker thread

**URL:** <https://forum.inductiveautomation.com/t/diagnosing-high-cpu-perspective-worker-thread/51989>\
**Category:** Ignition\
**Created:** [October 15, 2021, 9:09am UTC](https://forum.inductiveautomation.com/t/diagnosing-high-cpu-perspective-worker-thread/51989 "2021-10-15T09:09:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexm](https://avatars.discourse-cdn.com/v4/letter/a/3da27b/32.png) [@alexm](https://forum.inductiveautomation.com/u/alexm)\
**Post date:** [October 15, 2021, 9:09am UTC](https://forum.inductiveautomation.com/t/diagnosing-high-cpu-perspective-worker-thread/51989/1 "2021-10-15T09:09:30Z")

</div>

I am currently facing the same issue. Is there a way of finding exactly what the thread comes from? For instance:

My highest thread is “perspective-worker-419, id=14625”. How can I spot exactly where this comes from?

Thanks

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 15, 2021, 2:25pm UTC](https://forum.inductiveautomation.com/t/diagnosing-high-cpu-perspective-worker-thread/51989/2 "2021-10-15T14:25:56Z")

</div>

Your best tool is the stack trace below the thread dump. It tells you exactly what the thread is trying to do when it’s consuming that CPU. You’ll then have to work backwards from what it’s doing to find where it’s being called (this is sometimes the tricky part) and make adjustments.