I recently updated an internal application from JSAPI 4.16 to 4.22 to evaluate the memory and performance improvements in the Feature Layers.
After the update, the application first off over 2,000 requests to the various Feature Layers, which results in a load time of over 3 minutes. The volume of services requests results in several hundred returning `ERR_INSUFFICIENT_RESOURCES` from the ArcGIS Server, too.
Our application loads a Webmap by ID from ArcGIS Online and creates about 20 stand-alone FeatureLayer objects that are used for querying that are not added to the map during start up.
It appears that many of the requests are for the gridded query strategy (different, sequential bounding boxes) of the Feature Layers, which I can understand, but didn't expect the volume of queries or such different startup behavior from 4.16.
Looking for advice on what approach I can take to isolate and control the amount of queries made by the FeatureLayer class and if there are any specific behaviors of the FeatureLayer that we should be aware of in the jump from 4.16 to 4.22 that might be exacerbating this issue.
Note: I have reviewed the Breaking Changes information and the Release Notes in general, but did not pick up any anything specific from those sources.
