Poor Slow Performance with Experience Builder

[TD1]

Created an Experience Builder app based on the same map/data that a WAB app was using. WAB is very quick panning/zooming but the Experience Builder app is painfully slow. 

We all pay good money for these tools and this is unacceptable.

This needs to be resolved ASAP as users don't want to use the app as its slower on the supposed "new and improved" Experience Builder

[TD1]

I'm glad that I'm not the only one who has experienced these performance issues.

ESRI - please listen to your users and delay the deprecation of WAB UNTIL the issues with experience builder are resolved.

[ericsamson_tract]

Not alone! I am using the developer version, and it's a shame because I have found it way easier to create widgets using react and typescript + with experience builder we get to use the new 4.x javascript SDK. I can create new functionality for my team in a just a day in experience builder. Always takes me longer in WAB.

But these performance issues are a real drag. When I called them about this a year ago, they just said I should remove the larger layers from the application. Obviously, this is not a solution when our workflows depend on those layers entirely.

[DanCopKac]

Hahahahaahahahahahahahahaahahaa love that suggestion!

"To ensure optimum performance in Experience Builder, we recommend not using any layers! Guarantee it'll be faster than WAB!"

[Ed_]

one thing could be to see if it has to with the ArcGIS Map SDK for JS? 
How CPU usage is being handled?
How efficient is memory allocation?
How efficient is garbage collection?
?cache?

[ericsamson_tract]

I can't speak to it too much, but just by watching the developer tools it seems like garbage collection is not as good as it is in WAB