Hi, I'm and end user and don't really have a solution for you, but my experience has been mixed with AppStream.
We are running ArcGIS Pro 3.2.0 in stream.standard.2xlarge AppStream instance. We have been using this setup for a couple of months for 2D workflows only. We don't do much with 3D data, but wouldn't even attempt any processing or display in AppStream!
So far we have found the performance to be highly variable...some days it's okay and usable, other days there is a lot of lag when clicking on menu items or just waiting for some action to happen.
We have run some simple benchmarking tools to try and isolate when/where the bottlenecks are happening, but haven't found anything definitive. These tests have been along the lines of:
- copy a feature class from an SDE enterprise DB to a local FGDB
- run a search cursor for records in SDE enterprise DB and local FGDB
- perform an intersect geoprocessing task
I recently found the deployment guide and it recommends using Compute/Memory optimised instances instead. I've requested our IT department to spin one up so that I can run some comparison tests.
We only have a small team (< 5), so unlikely that the AppStream fleet resources are being exhausted, but we don't have any visibility of what is happening behind the scenes so don't know if we are under provisioned.
At times when the performance becomes so poor that you're waiting 30 seconds for a definition query to apply to a feature layer, the only option is to save, quit, and restart the AppStream session. Even then, there is no guarantee that the performance will be any better when it comes back up!
Overall, it's been quite frustrating to get the setup to a reliable and usable state.
