search

mjaakko / NeoStumbler

New stumbler application for contributing data to geolocation services
MIT License
103 stars 9 forks source link

Improve map performance #237

Closed mjaakko closed 4 hours ago

mjaakko commented 4 days ago

The map view becomes quite laggy after a large amount of reports have been made. Currently all reports are queried from the DB and hexagons are created for all of them. Performance could be improved by checking the map bounds and only fetching and rendering data inside them

AtmosphericIgnition commented 3 days ago

Just to add some more info on this:

I currently have 48148 reports in total, 200k WiFi APs, 9k cell towers, and 4500 Bluetooth beacons. When looking at the map right now, I get one frame maybe every 2-3 seconds. Eventually, if the map is in view, I will get a "NeoStumbler is not responding" system pop-up. If I choose to "wait", the pop-up will keep appearing every ~5 seconds, the only option at that point is killing the app. Attached are some logs I got after I killed the app.

NeoStumbler log bf2907dbbadc.txt

AtmosphericIgnition commented 2 days ago

I saw that this commit is supposed to address the performance issue. I tried downloading the APK automatically generated by GitHub for each commit, but there is no way for me to transfer my database from the proper release into the updated debug APK to test this fix. If you publish a new pre-release, I can test the fix.

mjaakko commented 8 hours ago

@AtmosphericIgnition 1.3.2-rc2 is now available

AtmosphericIgnition commented 7 hours ago

Seems to have fixed the issue for me. No longer freezes and runs smoothly.