Select to view content in your preferred language

Sketch graphics are slow on polyline and polygon click creation (4.29 JS API)

257
6
04-23-2024 04:20 PM
GILBERTNG1
New Contributor III

The refresh rate of temporary sketch graphics appear to be significantly slower in 4.29 JS API compared to 4.26. Basically, the temporary sketch graphics takes time to "catch up" to the mouse between each vertex click, when sketching a polyline or polygon. Compared to 4.29, the temporary sketch graphics are smooth in 4.26. To demonstrate this, here are two examples: 

Example 1 Using SketchViewModel: Replace "4.29" with "4.26" in lines 11 and 12, click on the top-right "Refresh" button, and then perform some polyline and polygon drawings to compare:

https://developers.arcgis.com/javascript/latest/sample-code/sandbox/?sample=sketch-viewmodel-styler 

Example 2 Using Sketch: Same as Example 1, but edit lines 8 and 9:

https://developers.arcgis.com/javascript/latest/sample-code/sandbox/?sample=sketch-geometries 

I tested this in the latest Chrome browser, on a Windows PC that has a 13th gen Intel i9 CPU. The same issue also applies to the Draw class, from my observations so far. We would like to know if there is a workaround, in order to complete custom application updates to 4.29 JS API. 

6 Replies
GILBERTNG1
New Contributor III

As a quick update, I only see this 4.26 vs 4.29 issue when remoted into the workstation via Windows remote desktop (RDP), even at the highest quality settings. The issue does not happen when directly accessing the examples without remoting in. 

0 Kudos
GILBERTNG1
New Contributor III

Another update: We found no issue at 1080P resolution in Chrome + Windows RDP, and zero issues in Edge web browser. The issue only comes up at a certain RDP monitor resolution, such as 4K. 

0 Kudos
GeoGalvanic
New Contributor

Hmmm, I'm wondering if something else changed in your setup.

 

I'm getting poor performance on chrome while RDP'd and on edge locally, however decent performance on firefox and chrome locally. All my monitors are at 1080p so that doesn't seem to be the cause.

 

I would think maybe a caching issue (if esri rolled out a sneaky fix) but I've cleared my cache, so I'm not sure.

0 Kudos
GILBERTNG1
New Contributor III

My best guess is network or WAN performance that is causing the RDP to "catch up" to a high HTML5 SVG graphics refresh or frame rate, since sketch seems to be smooth at 4k RDP resolution today on my end. 

0 Kudos
AndyGup
Esri Regular Contributor

Hi @GILBERTNG1  thanks for reporting, this sounds like RDP performance issues that are unrelated to the JavaScript SDK. Does the host machine have a GPU and is this a shared machine?  No GPU can have a significant affect on rendering performance. And, multiple users can cause variations in performance.

There are many interrelated factors that can affect RDP session performance such as screen resolution, connectivity speeds (like you mentioned), number and type of users on the machine, GPU, etc. 4K RDP resolution requires a high-bandwidth connection with consistent low-latency. Here's an informative Microsoft article on the topic: https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-bandwidth and here are some network guidelines for display resolutions: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/network-guidance#dis....

0 Kudos
GILBERTNG1
New Contributor III

Thanks for the response. I am no longer experiencing this issue, and it can be closed. RDP host machine is a newer model physical workstation with midrange Nvidia GPU, which is not shared with other users. It is possible that the issue going away this week was correlated with a recent upgrade from 1G to 10G network backbone at the office.  

0 Kudos