[Bug]: Map performance issues

[dpedu]

Contact Details

Reply here :)

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

• I actually read this list, and should be taken seriously.

Affected app version

2.7.12-google, 2.7.13-google

Affected Android version

Android 16

Affected phone model

Google Pixel 9a

Affected node model

N/A

Affected node firmware version

N/A

Steps to reproduce the bug

1. Acquire a large number of nodes
2. Zoom into a portion of the map where there are few or no nodes
3. See that it performs poorly - input lag, single-digit fps, high CPU usage

Actual behavior

Maps performs poorly - input lag, single-digit fps, high CPU usage.

Expected behavior

Map performs decently regardless of zoom level.

Screenshots/Screen recordings

https://www.youtube.com/watch?v=o3Uu2-eyW2c

Relevant log output

N/A

Additional information

I have ~2000 nodes in my app.

When I zoom out on the map - for example, such that I can see the entire United States - performance is decent.

When I zoom into a narrow area on the map, where there are few (~3) or even zero nodes, performance dips. The map is rendered at single-digit frames per second, input lag increases, etc.

I would have expected the full zoom out where more content is shown to perform worse than a narrow zoom where little content is shown. This is strange, so I suspect something is wrong.

[rjDipcord]

Can confirm I am experiencing the same behavior on a Google Pixel 10 Pro XL.

When zoomed out, the nodes condense into the larger groups to take up less screen space and make it easier to see where the dense concentrations of nodes are without the high number of entities on screen.

When zoomed in, these condenesed groups expand, increasing the entity count. I suspect something has changed with this mechanism, and it has caused performance issues related the quantity of entities rendered.

I still notice jarring movement and low FPS, even when zoomed all the way out.

Also on 2.7.12

[dpedu]

I've updated to the newly released v2.7.13 (Play store version) and map performance seems about the same.

[laundmo]

Its likely that #3785 would, if not resolve, at least affect this, as its a different map renderer altogether

[DaneEvans]

@laundmo Feel free to pick it up then.

[jamesarich]

Displaying thousands of datapoints/markers is probably a limitation of the google maps library and would probably choke maplibre also. 🤷 performance at extreme scale is not a big priority.

[laundmo]

From what i've seen in other apps using maplibre, it can handle quite a lot, which is why i said that

[jamesarich]

Still not a huge priority - the app isn't really intended to be used at extreme scales, this isn't pokemon - you don't need to collect em all.

Set some favorites or export some nodes you need to retain and reset your db.

[jamesarich]

Filters exist to limit the amount of nodes visible, which may improve performance as well.

[laundmo]

Dunno why you're arguing here, i didn't say it should be, just that ime maplibre handles it better

i mean, i also find the lack of large scale mesh and node visualization and analysis tools for meshtastic disappointing, but thats wholly unrelated to this issue

[dpedu]

Filters exist to limit the amount of nodes visible, which may improve performance as well.

While this is a reasonable workaround, it is quite easy to accidentally tap the filter too broad of off entirely, which causes the app to slow to a crawl or freeze up entirely. This much shouldn't happen.

[github-actions]

This issue has not had any comment or update in the last 30 days. If it is still relevant, please post update comments. If no comments are made, this issue will be closed in 7 days.

[laundmo]

map implementation hasn't changed, so the only way this could've improved is if some other part got optimized, which i also don't think happened