This object is in archive!
After update 3.15.2 hiding points takes a while
Closed
Hi,
I have a category of points of my pocket queries.
It contains about 28000 geocaches.
Before the update of today (yesterday?) hiding all the points would take about 10 seconds maybe?
But now it takes more than 10 minutes to hide them all or the app even crashes while trying?
Is this a know bug or is it new?
Thank you in advance.
Kind regards, Cethyn
The same problem 
Hello Cethyn,
hiding may take a little longer then in previous versions, it is correct, but 10 minutes and crash, this has to be some problem in Locus. I'll check it, thanks.
Hello Cethyn,
hiding may take a little longer then in previous versions, it is correct, but 10 minutes and crash, this has to be some problem in Locus. I'll check it, thanks.
Thank you for the quick response.
Good luck :)
Thank you for the quick response.
Good luck :)
Hello,
I was fighting with it for a while now and I'm quite surprised, Locus was previously able to handle so much caches on a map at once. Anyway now it won't be possible, sorry. On my device, unload of 25.000 caches took more then 30 seconds. It is now reduced to to around 1/3. Still not perfect, but a lot better. Problems with memory anyway remains and I highly suggest to keep number of visible points (mainly caches) below around 10.000 points at once, not more.
I can imagine how to this all better now, but it will require completely changed structure of internal database and I believe that such limitation isn't so bad at all.
Thanks for understanding.
Hello,
I was fighting with it for a while now and I'm quite surprised, Locus was previously able to handle so much caches on a map at once. Anyway now it won't be possible, sorry. On my device, unload of 25.000 caches took more then 30 seconds. It is now reduced to to around 1/3. Still not perfect, but a lot better. Problems with memory anyway remains and I highly suggest to keep number of visible points (mainly caches) below around 10.000 points at once, not more.
I can imagine how to this all better now, but it will require completely changed structure of internal database and I believe that such limitation isn't so bad at all.
Thanks for understanding.
Hi,
Thank you so much for trying, too bad it can't be solved.
I will try your suggestion or else I will try to work around it.
Kind regards, Cethyn
Hi,
Thank you so much for trying, too bad it can't be solved.
I will try your suggestion or else I will try to work around it.
Kind regards, Cethyn
I just tried you suggestion to have lists under 10000. It works perfect, now they hide in under 4 seconds I guess.
Weird but anyway thank you!
I just tried you suggestion to have lists under 10000. It works perfect, now they hide in under 4 seconds I guess.
Weird but anyway thank you!
You are welcome.
Just to give you some more information - in new version is created system that Locus remember exact state of visible waypoints for every cache when you display and hide it. And when you try to load a cache on a map, Locus firstly test if there was previously any waypoint visible or if you have enabled some settings in "auto-loading of waypoints". If any of this condition is correct, Locus needs to load whole cache to get it's waypoints (here is a main problem because there is no method to load just waypoints) and display them.
When you hide a cache, Locus then search for waypoints attached to cache and remember it's visibility state. Here is another problem - in case of too much waypoints on a map, search takes quite long.
Hope this brings a little light to this problematic.
EDIT: anyway as I wrote, it will be a lot better in next version. I've found a few places that helped.
You are welcome.
Just to give you some more information - in new version is created system that Locus remember exact state of visible waypoints for every cache when you display and hide it. And when you try to load a cache on a map, Locus firstly test if there was previously any waypoint visible or if you have enabled some settings in "auto-loading of waypoints". If any of this condition is correct, Locus needs to load whole cache to get it's waypoints (here is a main problem because there is no method to load just waypoints) and display them.
When you hide a cache, Locus then search for waypoints attached to cache and remember it's visibility state. Here is another problem - in case of too much waypoints on a map, search takes quite long.
Hope this brings a little light to this problematic.
EDIT: anyway as I wrote, it will be a lot better in next version. I've found a few places that helped.
I understand. (Fellow developer, I hate fixing performance issues ;) )I will test it again in the next version, thank you.
Is it ok to attach my findings of the next version in this thread when I have tested them?
I understand. (Fellow developer, I hate fixing performance issues ;) )I will test it again in the next version, thank you.
Is it ok to attach my findings of the next version in this thread when I have tested them?
Replies have been locked on this page!