I have the use case to cluster markers by a property (layer) - resulting in having multiple clusters.
Using the sample app - with NonHierarchicalViewBasedAlgorithm (https://github.com/googlemaps/android-maps-compose/issues/380) - adding 10 clusters with each 400 markers - this results already in skipped frames in a release build on a physical device.
I have the use case to cluster markers by a property (layer) - resulting in having multiple clusters.
Using the sample app - with
NonHierarchicalViewBasedAlgorithm
(https://github.com/googlemaps/android-maps-compose/issues/380) - adding 10 clusters with each 400 markers - this results already in skipped frames in a release build on a physical device.Any ideas to improve performance here?
Here is the sample: https://github.com/googlemaps/android-maps-compose/compare/main...cwsiteplan:android-maps-compose:bug/performance-clustering
It gets worse when i try to group the markers not only by one property but two. My use case is that i have different types of markers which are assigned to layers. I need to group first by layer and then by type - resulting in potentially 20-30 clusters or so. This results in a lot of UI lag. Sample here: https://github.com/googlemaps/android-maps-compose/compare/main...cwsiteplan:android-maps-compose:bug/performance-clustering-types