Desktop performance, AGOL servers and (maybe) Starlink...

[TanithLives]

G'day all

As with many users here, I have a problem with the performance I am getting from ArcPro. It's always been a bit plodding, but over the last two weeks it's taken a real downturn. I have been through all the conceivable forums and advice on setting the machine to work as well as possible - with the machine I am using being relatively spec (32 GB RAM, RTX 3060 GPU, 2.4 Mhz). I work locally, bar the use of REST servers to hook into data and basemaps. From what I can tell it's these servers that are causing the issue, with Diagnostic Monitor showing MapServer-related slowdowns. Sometimes the basemap imagery I use (usualy World Imagery) doesn't even load and just red-Xs itself. Sometimes it is perfectly fine. However, this is only happening in ArcPRO. When I switch over to QGIS, I can bring in the data no problems with QGIS's usual alacrity.

I am just wondering if anybody else has experienced this in the last 2-3 weeks? Is there something wider going on with AGOL services? Whenever it happens I check the online service monitor and it always says the service is up and running. The only thing that has changed at my end is I have switched to Starlink in that time...in which case, has anybody experienced similar issues with this ISP??

Cheers in hope...  

[Robert_LeClair]

I wonder if your IT team needs to add exceptions to their firewall to allow network traffic (i.e. the basemaps)?

You can learn more here:
What Are the Required Firewall Domain Exceptions to Access ArcGIS Online?
REV_AGOL_Domain_Requirements.pdf

[BillFox]

Starlink WiFi

or

Starlink Ethernet/DHCP "hard wired"

the hardwire should give lower latency

[TanithLives]

G'day @BillFox and @Robert_LeClair . Thanks for the replies. The connection already is hardwired, so that rules that out. Also, this is from my home office, so not being interrupted by unwarranted IT intervention. It's a frustrating mystery.

[Robert_LeClair]

G'day @TanithLives - in looking at the internals a bit more about this issue, here's some troubleshooting items to consider.

Here are some steps you can try:

• Use Diagnostic Monitor to identify whether the slow calls are mainly ExportMapImage (map image layer draws) or query (feature layer querying). This helps pick the right mitigation. (Doc referenced in Esri KB: ArcGIS Diagnostic Monitor)
• If the layer is mostly for visualization, prefer cached layers (hosted tile or vector tile layers) instead of dynamic MapServer drawing. Vector/raster tiles are designed for fast display and generally perform better over higher-latency connections. (Optimize web maps, layers and apps, Manage hosted tile layers)
• Set visible scale ranges so layers don’t draw/query huge extents at small scales (a common cause of slow querying/drawing). (Esri Support KB 000030619)
• If you’re working with hosted feature layers, consider hosted feature layer views to create a “lighter” view for Pro users (different settings, potentially less content to draw/query). (Optimize web maps, layers and apps)
• If editing/working interactively, use Pro’s Feature Cache controls (manual fill/empty, avoid auto-cache thrash) as noted in the KB. (Esri Support KB 000030619)