Visits site sometimes not responding + reverse geocoding adding nonames in suggested Visits
Describe the bug
-
Visits site sometimes "not responding" or taking way longer when opening a page higher than 15-20 or confirming a visit there. (Screenshot1) Loading times are way faster on the first 10-15 pages.
-
Visits also show "suggested place" for everything even though I re-ran reverse geocoding after enabling it firstly and then on a second try after setting up a photon host just for this re-ran it again. Still everything in there only shows "suggested place". (Screenshot2) Or am I wrong and its only showing the name when you click on map? There are sometimes entries there but not for all of them, even though there is literally a hotel or similar shown on the map. (Screenshot3)
Version 0.12.3
To Reproduce Steps to reproduce the behavior:
- Go to 'Visits'
- Click on 'Last or a page higher than 15-20'
- Site "not respondig" or loading really long
- After it loaded confirming a location also takes ages
Expected behavior
-
Same behavior for Visits on higher page numbers as in the first 10. (loading speed)
-
Reverse geocoding to actually provide a name for visits?
Screenshots
1
2
3
Logs Can't find any errors or anything in the container logs
Additional context Temporarily I had the container running on 10 cores and 8GB Ram + 8GB Swap with 4 sidekiqs (didnt change visit loading speed but I used it for import/reverse geocoding speed)
I'd like to link this thread here to provide some context: https://github.com/Freika/dawarich/discussions/298
What's the current expected situation with visits after the recent improvements? I'm still encountering this sort of freezing frequently with anything exceeding a handful of suggested visits (even after deleting backlog of suggested visits and resuggesting a few days or a week at a time) and not sure if it's an issue with my setup (i.e. too many points for good performance?), general "work in progress" of the feature, or something else. Just trying to calibrate what my expectations should be
The visits page haven't been worked on yet, so yes, it's still not optimized. Will work on it this summer hopefully :) Maybe rather sooner than later!
Fixed in https://github.com/Freika/dawarich/releases/tag/0.30.0