Hi there,
The sample you referenced is not related to supportsCacheHint. At 4.19, we improved of performance of point FeatureLayers to fetch all its features at once from the server. Once loaded, the features won't need to be re-requested from the server, which will make future redraws after panning and zooming much faster.
Point feature layer fetches all of its features at once if the following conditions are met:
- featureCount = 0-80,000, fetch all features
- featureCount = 80,001-400,000, fetch all features if view's initial extent is greater than 10% of the layer's data extent (i.e., if we are not super zoomed)
The point feature layer will request features as needed (do not fetch all features) if
1. Point layer is editable
2. If layer.refreshInterval is set and lastEditDate is `undefined` in the metadata.
The point layer referenced in the sample fetches all of features as once since it meets the requirements mentioned above.
If you enabled caching on your enterprise service (caching always enabled for hosted feature services), the JS API will take advantage of the server caching as it makes tile query requests for display. Please review this document for more info about caching.
If you are sending query requests from your app and the query params always the same you can set the cacheHint property on your query object.
https://next.sites.afd.arcgis.com/javascript/latest/api-reference/esri-rest-support-Query.html#cache...
