# MappView performance

**URL:** <https://community.br-automation.com/t/mappview-performance/1410>\
**Category:** HMI & Visualization\
**Tags:** mapp-view\
**Created:** [December 7, 2023, 8:30am UTC](https://community.br-automation.com/t/mappview-performance/1410 "2023-12-07T08:30:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![wagner2a](https://avatars.discourse-cdn.com/v4/letter/w/FF8800/32.png) [@wagner2a](https://community.br-automation.com/u/wagner2a)\
**Post date:** [December 7, 2023, 3:08pm UTC](https://community.br-automation.com/t/mappview-performance/1410/3 "2023-12-07T15:08:56Z")

</div>

Hello,  
just to add some experience to the Help Guidlines…

1. Hardware:

- More Hardware Performance helps more
- In most of the cases the bottleneck is at Client Hardware side
- Please consider especially the number of cores and how many are available in your case (see [APC3100 100% CPU usage while using the MappView in chrome](https://community.br-automation.com/t/apc3100-100-cpu-usage-while-using-the-mappview-in-chrome/926/1))

1. Software:

- E. g. the tab control widget pose the risk that there are a lot of widgets on one page, which can lead to very long loading times. In that case it is maybe better to work with a contencontrolwidget- there is a sample in the mvHighlights Project at the widget overview Page  
 ![image](https://europe1.discourse-cdn.com/brcommunity/original/1X/ad65dbe60a19de9bca4a05df8aff7423983d4bfc.png)
- caching/precaching helps to improve the operation experience a little bit- but there are cases where it is neccessary to switch to a hardware with higher Performance

---

_[View the full topic](https://community.br-automation.com/t/mappview-performance/1410)._