Select to view content in your preferred language

Why ExB so memory hungry?

226
7
Friday
JoabelBarbieri
Frequent Contributor

Hello Esri Community and Experience Builder developers,

I am troubleshooting a performance issue with an ArcGIS Experience Builder application and would appreciate feedback from the community and Esri development team.

The application is causing very high resource usage in the browser:

Memory usage: ~1.75 GB RAM
CPU usage: ~140%+ (multiple cores)
Browser: Chrome/Edge
Impact: Laptop fan runs continuously, system becomes sluggish
The issue occurs while running the Experience Builder application (not just during initial loading). The browser process remains under heavy CPU load.

I am trying to determine whether this is caused by:

A specific widget behavior
Map rendering/WebGL issues
Feature layer complexity
Excessive queries or refresh cycles
A known Experience Builder performance issue
Things I would like advice on:

Are there recommended tools or methods to identify which Experience Builder widget or map layer is consuming CPU?
Are there known performance issues with certain widgets (Map, List, Table, Filter, Chart, etc.)?
Are there best practices for diagnosing high CPU usage in Experience Builder apps?
Are there browser developer tools, ArcGIS logs, or debugging methods that can help isolate the cause?
Current observations:

Chrome Task Manager shows the Experience Builder tab consuming ~1.75 GB memory.
CPU usage frequently exceeds 100%.
The behavior appears related to the running application rather than the initial loading process.
I have already done:

Reducing visible layers
Simplifying symbology
Limiting labels
Optimizing feature services
Testing published vs. builder mode
However, I would like to identify the actual source of the CPU usage rather than blindly removing functionality.

If anyone from the Experience Builder team or experienced developers has suggestions for profiling or debugging this type of issue, I would greatly appreciate your guidance.

Thank you!

7 Replies
JudithWammack
Frequent Contributor

@JoabelBarbieri , I have a quick question. Is the map where you're experiencing this issue publicly accessible? I used to encounter similar problems, but after making several browser-related changes, the issues were resolved.

I'm wondering if those same changes might help in your situation. If the map is available, I'd be happy to test it.

For context, one of my department's maps contains approximately 98 layers within a single image layer. We experienced performance issues early on, but I was able to resolve them through research and browser configuration changes, without assistance from ESRI.

 

0 Kudos
MichaelVolz
Esteemed Contributor

Judith:

Can you share your research and browser configuration changes to the general community who might be having or will have in the future browser performance issues?

Thank you

0 Kudos
JudithWammack
Frequent Contributor

@MichaelVolz & @JoabelBarbieri 

The map currently supports about 800 users per day. We encountered several issues during the initial rollout, but after extensive research, testing, and optimization, the map has now been running successfully for approximately two years. 

Below is the troubleshooting checklist we have developed based on our experience. These steps are primarily intended for users who are experiencing performance or display issues, particularly users running the map in a virtual machine or on computer without dedicated graphics hardware.

Checklist below:

  • Install the latest Microsoft. NET Runtime x64

Download and install the most recent Microsoft .NET Runtime. We have not identified a definitive reason why this resolves the issue, but it appears to improve performance for some users. It seems to be especially helpful for users running Windows 10 in a virtual machine.

  • Verify that the browser is supported by ESRI

Confirm that the user's browser meets ESRI current supported-browser requirements: Supported Browsers

  • Enable hardware graphics acceleration

In the browser, go to Settings - System and verify that "Use graphics acceleration when available" is enabled. After changing this setting, restart the browser if prompted.

  • Enable "Override software rendering list"

Navigate to browser://flags and locate "Override software rendering list." Enable this setting and restart the browser. Example: chrome://flags

NOTE: This is an experimental browser setting and should be used with caution. It forces the browser to use graphics acceleration even when the hardware would normally be excluded by the browser's software-rendering compatibility list. On unsupported hardware, this can potentially cause instability or graphical issues. However, based on our testing and usage, we have kept this setting enabled without encountering those problems.

Additional NOTES:

My personal computer runs Windows 11 and has a dedicated graphics card, and I do not need to make any of these configuration changes for the map to perform properly.

Based on our experience, these troubleshooting steps are primarily applicable to users who do not have dedicated graphics hardware, are using a virtual machine, or are otherwise experiencing graphics-related performance issues. Users with modern computers and dedicated graphics cards generally should not need to modify these settings except for "Enable hardware graphics acceleration."

Disclaimer: These steps are based on our own testing and experience with the map. Some are recommended by ESRI, while others are things we have found that helped. They may not fix every issue, so please do some research before making changes to your browser or computer settings, especially when using experimental settings.

0 Kudos
JoabelBarbieri
Frequent Contributor

No, it's only available inside the company. 70 users top.

0 Kudos
TD1
by
Frequent Contributor
JoabelBarbieri
Frequent Contributor

Wow..huge thread over there. At least I'm glad that I'm not the only one having this issue. ExB is painfully slow

0 Kudos
TD1
by
Frequent Contributor

@JoabelBarbieri Yes lots of others have the same issue. ESRI doesn't seem to believe it's an issue. I have also put in bugs with ESRI support.

Be sure to put in your comments in that other thread as well to make it more visible to ESRI. https://community.esri.com/t5/arcgis-experience-builder-questions/poor-slow-performance-with-experie...

0 Kudos