Poor map performance with many markers/layers

[Bubu]

The map view in the WeShare app is unusably slow to respond. It seems to do lot's of stuff in the UI thread.
On a phone with play services the app works fine.

So this is most likely some of the overlay things that are slow here. The map works fine until the car POIs are loaded then it stops responding to input after scroll/zoom for a couple of seconds.

You can also watch the progress of the poi clustering algorithm... it takes a couple of seconds when there's a lot going on on the map 🙈

[Nesaijn]

Seems to be the same with the car2go app

[Bubu]

Working hypothesis from @mar-v-in:

Too many map layers (one for every marker by default) slow down mapbox to a crawl. Could potentially be solved by merging same z-level markers into one layer.

[ildar]

Is mapbox/mapbox-gl-native#2444 in the mapbox release that MicroG's using? Mapbox guys say it improves the performance.

[ghost]

I think it will be good to change the title of the issue to something like "Poor map performance in apps". Because this issue is not about only WeShare app anymore.

I have the same issue in EQInfo ( https://play.google.com/store/apps/details?id=de.gempa.android.eqinfo&hl=en_US&gl=US ).

When there is displayed not so much earthquakes, then performance is good. But with thousands of them map becomes slower. Especially when I'm changing its scale.

[mlell]

Still a problem in 2022¹. Car/Bike sharing apps like Jelbi (Berlin) or Lime are barely usable (Fairphone 3, Android 10, microG 0.2.24.214816-48)
———
^{1 Of course I know and acknowledge that this is free time work by other people, just in case this sounds unfriendly}