Issues with webGL performance and support

1180
4
Jump to solution
03-04-2021 10:24 AM
dmarkbreiter
New Contributor II

 

Problem

I've been developing a web application for the first time using the JS API. When testing the performance of the website, I've had perfectly snappy use on relatively new hardware (such as my Surface Laptop 3 8GB RAM, Chrome v88) but cripplingly slow use on somewhat old hardware (MacBook Pro 13" 2016 8GB RAM, MacBook Pro 15" 2014 8GB RAM, Dell Inspiron 15 5000 2017 8GB RAM, all running Chrome v88). 

Link to web app in development:

 

Troubleshooting

Considering how these "older" hardware aren't very old, the laggy performance is troubling. At first I thought it might be a basemap or feature service that was slowing down the application, but when I tested sample apps on the developer page for the API, I had equally if not slower performance.

Example apps linked below:

The above apps work perfectly fine on my Surface Laptop 3, but absolutely limp along on the other tested hardware configs. 

UPDATE I

Looking at my own app, I see that two feature services (LAU_Localities_View and SoCal_Counties) have multiple GET requests at page load. I've included the Query String Parameters of one of them below:

The first thing that strikes me as weird is the low maxRecordCountFactor of 3.

 

 

 

f: pbf
geometry: {"spatialReference":{"latestWkid":3857,"wkid":102100},"xmin":-13149614.849954996,"ymin":3757032.814274987,"xmax":-12993071.816026995,"ymax":3913575.8482029866}
maxRecordCountFactor: 3
resultOffset: 0
resultRecordCount: 8000
where: 1=1
orderByFields: OBJECTID ASC
outFields: OBJECTID
outSR: 102100
quantizationParameters: {"extent":{"spatialReference":{"latestWkid":3857,"wkid":102100},"xmin":-13149614.849954996,"ymin":3757032.814274987,"xmax":-12993071.816026995,"ymax":3913575.8482029866},"mode":"view","originPosition":"upperLeft","tolerance":305.74811314062526}
resultType: tile
spatialRel: esriSpatialRelIntersects
geometryType: esriGeometryEnvelope
inSR: 102100

 

UPDATE II

It looks like the warning regarding graphics driver support for webGL is the culprit. Chromium based browsers seemed to suffer, but the issue seemed to only persist for about a day (no updates were performed on Edge 88 or macOS Catalina).

Question

Is this the expected behavior/performance of web applications built using the API?

If not, how can I make my application more performant on a variety of hardware configs? Even panning around a basemap feels and looks choppy on this hardware. 

 

1 Solution

Accepted Solutions
AndyGup
Esri Regular Contributor

Yes, we have seen those errors before. The error is saying that there was a bug in the display driver and a workaround was applied by OS. Best thing is to update the drivers. Make sure you are on MacOS 10.15.7 with the latest supplemental or update to Big Sur, if you are able. And, also for the best performance make sure you have the latest browser version installed. Edge 89 should be the latest.

View solution in original post

4 Replies
dmarkbreiter
New Contributor II

It would appear that the issue is with Esri's WebGl engine and it not working with the machine's graphics driver as evidenced by the following console warning on Chrome based browsers:

[esri.views.2d.engine.webgl.WebGLDriverTest] A problem was detected with your graphics driver. Your driver does not appear to honor sampler precision specifiers, which may result in rendering issues due to numerical instability. We recommend ensuring that your drivers have been updated to the latest version. Applying lowp sampler workaround. [0.0.0.0]

When the web apps linked in the question were tested on FireFox 86, they worked perfectly fine and without the warning above.

An answer to this question was posted by me on StackOverflow

0 Kudos
AndyGup
Esri Regular Contributor

Interesting, which hardware are you seeing the error on? I just tested Examples 1 and 3 from above on a 2013 MacBook Pro 8GB RAM, MacOS 11.2.1. Using Chrome 89 I'm not seeing the same warning and the apps were usable. Also note, Examples 2 and 3 are using older versions of the JS API. The latest version is 4.18.

0 Kudos
dmarkbreiter
New Contributor II

@AndyGup  How weird. I'm running on a 13" 2016 MacBook Pro i5 8GM RAM macOS 10.15  on Chrome 89. Suddenly, as of the posting of this comment, the warning is now gone and the apps work... Has this warning been reported previously and is there anyway to ensure that it does not impact performance again? 

UPDATE

I was able to reproduce the warning on (Chromium) Edge 88 on the Macbook Pro but not Chrome... 

0 Kudos
AndyGup
Esri Regular Contributor

Yes, we have seen those errors before. The error is saying that there was a bug in the display driver and a workaround was applied by OS. Best thing is to update the drivers. Make sure you are on MacOS 10.15.7 with the latest supplemental or update to Big Sur, if you are able. And, also for the best performance make sure you have the latest browser version installed. Edge 89 should be the latest.

View solution in original post