Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issue when using multiple clusters #525

Open
cwsiteplan opened this issue Feb 13, 2024 · 0 comments
Open

Performance issue when using multiple clusters #525

cwsiteplan opened this issue Feb 13, 2024 · 0 comments
Labels
triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@cwsiteplan
Copy link

cwsiteplan commented Feb 13, 2024

I have the use case to cluster markers by a property (layer) - resulting in having multiple clusters.

Using the sample app - with NonHierarchicalViewBasedAlgorithm (#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: 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: main...cwsiteplan:android-maps-compose:bug/performance-clustering-types

@cwsiteplan cwsiteplan added triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

1 participant