FeatureLayer performance: is it possible to disable multi-lods?

[LittleTurtle]

Hello,

I am trying to migrate my app from v3 to v4.31 but I am having performances issues with my FeatureLayer while zooming. The performances issues do not seem to have a link with this bug https://support.esri.com/en-us/bug/arcgis-api-for-javascript-4x-is-rendering-slower-and-la-bug-00011... since I have implemented the fix but it does not improve the performances that much. 

It seems that in v3 with snapshot mode enabled, the FeatureLayer was only displayed with a mono-lod so the rendering was smooth. I am trying to reproduce this behavior in v4 but it does seem to have a solution.

Do you have any idea how to implement it or to upgrade the performances?

[LittleTurtle]

Ok so I might have been a bit confusing. What I have seen is that in V3, all my features are rendered on the map with the maximum geometry precision ; and when I zoom in I don't have to render the features again.

But in v4, it renders the features with a certain geometry precision and when you zoom in it rerenders these layers with another geometry precision... I would like to disabled that to come back to v3 method for performance issues if that's possible.

[SamEngel]

Hi @LittleTurtle! Are you able to share a codepen (or something similar) with an app that shows the problem?

[LittleTurtle]

Ok so I have searched a little bit more what my problem was and it is that in v3 I was using my FeatureLayer with "mode: 'SNAPHOT' and I am not able to reproduce this behavior since this mode does not exist in v4 and is not planned (https://developers.arcgis.com/javascript/latest/functionality-matrix/#featurelayer)

You can see from this v3 example that the FeatureLayer with SNAPSHOT mode enabled is not recalculating the polygon geometries everytime it zooms in or out (https://developers.arcgis.com/javascript/3/sandbox/sandbox.html?sample=fl_hover)

I don't really know what to do now since the performance while zooming/panning the map are worse than in v3, it is difficult to switch to v4. Is there a workaround to reproduce this behavior in v4?