# Choosing Ignition Client CPUs

**URL:** <https://forum.inductiveautomation.com/t/choosing-ignition-client-cpus/34183>\
**Category:** Ignition\
**Created:** [April 24, 2020, 2:42am UTC](https://forum.inductiveautomation.com/t/choosing-ignition-client-cpus/34183 "2020-04-24T02:42:04Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 24, 2020, 11:59am UTC](https://forum.inductiveautomation.com/t/choosing-ignition-client-cpus/34183/6 "2020-04-24T11:59:58Z")

</div>

> [@nminchin](#):
>
> The over VPN issues only occur when users try to access ignition from home to check on alarms etc.

This is common if you make the mistake of using `runScript` in a binding to execute alarm functions, use the `isAlarmActive` expression in a client binding, or do anything else that requires a request to the gateway on the UI thread (as @pturmel already mentioned).

---

_[View the full topic](https://forum.inductiveautomation.com/t/choosing-ignition-client-cpus/34183)._