# Best practices for monitoring performance of scale-out enterprise architecture

**URL:** <https://forum.inductiveautomation.com/t/best-practices-for-monitoring-performance-of-scale-out-enterprise-architecture/87571>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 19, 2024, 4:55pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-monitoring-performance-of-scale-out-enterprise-architecture/87571 "2024-03-19T16:55:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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 19, 2024, 5:54pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-monitoring-performance-of-scale-out-enterprise-architecture/87571/2 "2024-03-19T17:54:42Z")

</div>

> [@David\_Nicks](#):
>
> any red flags

Yeah, RAM.

See this discussion:

> [@Microsoft Virtual Machine Suggestion](https://forum.inductiveautomation.com/t/microsoft-virtual-machine-suggestion/86787/5):
>
> After going through that sizing guide, I'd add another vCPU for every 4-8 Perspective clients (of pretty much any kind), a GB of gateway RAM for every 4-8 light-duty Perspective clients, and 2-4GB of gateway RAM for every heavy-duty Perspective client. "Light duty" would be single page Perspective apps running in Workstation, or Mobile, or single-tab browser sessions, displaying dashboards with real-time tags, up to an hour (-ish) of real-time trends, and pre-computed statistics for longer time…

---

_[View the full topic](https://forum.inductiveautomation.com/t/best-practices-for-monitoring-performance-of-scale-out-enterprise-architecture/87571)._
