Beginning at version 2.1 (we haven’t tested 2.0), our ArcGIS Online users have been complaining about very slow response times when consuming AGOL Web Maps. The drawing response time seems to be a tiny bit better with 2.4, but the querying response time is still painfully slow. In this example, it takes some 30 seconds for the popup to show up.
It seems that all the features must be completely drawn before any popup could be treated. Doing some investigation with Fiddler, we found out that the queries for the popups (/query?f=json) always seem to be treated after all the other queries that return PBF data (/query?f=pbf).
Is there a reason why the calls are treated in that strict order? Could the popups be prioritized over the drawings?
These slow response times with the 2.x versions force us to be stuck at – the now retired – version 1.18. We have been told that the quicker response times of 1.18 have something to do with an implicit MaxRecordCount of 2000 features that is embedded in this version of the software. If this statement is true, could the MaxRecordCount of AGOL resources be controlled by the administrators in the configuration file in a future release of the software?
Sadly, with these recurrent slow response times with AGOL resources, we are now considering moving to another solution than ArcGIS Earth…