Latest Contributions by mgeorge

@AFackler_NAPSG it sounds like your driver is crashing, which would indicate a problem with the device. You could try running other gpu-accelerated applications and see if they also crash. If so, you may need to contact Framework and see if you can do a warranty repair, esp. if the device is new.  ... View more

@EricLake1 yes this is using AGOL hosted here, though the cold cache times shouldn't be that bad for this either (you can test this yourself by adding a definition expression like 4=4 to the layer). Also note that if you change the initial map zoom for this to be something like 12, the map will instead use tile queries. Is your backend actually bandwidth limited or are you seeing slow db timings? If it's the latter, deploying a cache in front of your service is probably the way to go.   ... View more

You can use the flag, but just be aware that this is not officially supported and likely will change. Some old versions of enterprise had a bug where querying for count was doing a select * from the database, and this flag was only really given out to work around that.  There's a very good chance that you will be significantly increasing the load on your backend by disabling snapshot, so just be careful to do some stress testing. 60k features is not a lot of data, and I would definitely not disable it in that case.  ... View more

Correction: we actually don't snapshot polygons/polylines for non-AGOL hosted at all yet. That is however planned for the near-term. So you shouldn't be seeing this in your environment.  ... View more

@EricLake1, in most cases snapshotting features reduces the load on the backend -- that's why we made this change. The alternative is making many tile queries (queries with extents) which then hit the spatial index on the backend. Enterprise can really chug with this as it doesn't yet support caching. Consider map load: assuming the map is full screen, then on a 1440p monitor you will be making a minimum of 15 tile queries if we don't use snapshot mode. As you interact with the map and pan around, that will result in many additional queries being made. With snapshotting the service however, once those initial queries are done, no additional queries need to be made. From our testing snapshotting significantly reduces load on the backend with realistic scenarios (many users interacting with a map over some period of time). We don't snapshot in every case, and it includes several factors like whether the service is editable, and count thresholds based on how zoomed out are you relative to the total layer's extent. For polygons & polylines, we make exceedslimit queries to check the vertex and feature count. At the moment, we only snapshot polygons & polylines if the count is 1000-2000 (exact value depends on the % of the layer you are looking at) If the layer isn't visible, I don't think you should be seeing any features being downloaded. For instance, I don't see pbf data queries getting made with https://codepen.io/matt9222/pen/YPyzaLO?editors=1000   ... View more

That's a valid option -- only downside is that GeoJSON is not a very efficient format, though should be fine for a few thousand points 👍 ... View more

Hmm strange -- it should be the default for AGOL hosted. Is there any kind of proxy that your service is running through? Also do you see if things are getting cached? Might be slow the first time, but I'd expect it to speed up once things are cached (there's a feature tile cache on the server and a CDN cache). ... View more

@EirikH sorry for the delay in getting back to you. For your use case, is the map on mobile, desktop or both? And which version of the API?  ... View more

Hi @FactSetResearchSystems, are you using a FeatureLayer? We should be downloading pages of 8k features. I'd make sure caching is enabled. Here's an example of a map loading about 350k features: https://codepen.io/matt9222/pen/MYYpPRK?editors=1000 ... View more

Hi @katsick,  Unfortunately due to how old these devices are & given that they are no longer supported by the manufacturer, we do not have plans to try and create a workaround this driver bug at the moment.  Matt ... View more

@FC_Basson unfortunately it looks like some of these old machines were recycled, but I was able to get access to a machine with an intel hd 4400 & am trying to reproduce.  To confirm, the issue can be see with https://developers.arcgis.com/javascript/latest/sample-code/intro-graphics/? Can it also be seen with https://developers.arcgis.com/javascript/latest/sample-code/layers-featurelayer/?  ... View more

@FC_Basson that processor actually came out in 2012 so it's probably 11-12 years old 😅. That said, I know we have an old Intel hd 3000/4000 device in storage somewhere as I remember installing some workarounds related to those in the past. ... View more

@FC_Basson, we're currently trying to get ahold of a device with similar specs.  ... View more

For those who are experiencing the flickering, do you still see here? with: https://bsvensson.github.io/various-tests/compare-webmaps/webmap.html?webmap=87e7f204fd1f4595ada62603359ec40c&api=https://jsdev.arcgis.com/next/ ... View more