This object is in archive!
What can I do to improve the performance of Locus?
Answered
Hello
I have noticed that the performance of Locus is getting bader from time to time on my device. At the first day, I installed Locus, it was very performant.
Can you give me some tipps to improve the performance of Locus. For example clearing any cache datas of locus or something else?
Do you think that the performance is getting bader, if you have many saved tracks or POI's?
What can I do, that Locus is as performant, as of the first day I installed Locus?
Thanks in advance!
The same question
Maybe a help topic in the online manual would be useful with general tips.
Maybe a help topic in the online manual would be useful with general tips.
Hi guys,
generally there is a few CPU consumers, that worth it to check:
- extra map layers - Map Overlays, WMS maps
- too much points and tracks - every device has own limits, so there are no exact numbers I may say, that since that Locus starts to be slower. I usually often use in "Data manager" > Points/Tracks tab > top button "Deselect all", which hide all points and in second tab also tracks in Locus that comes from database
- in case of geocaches, this limit is little bit lower as they are more complicated to draw on a map. Visible waypoints slow down also a little more then common points. In case of custom icons for geocaching, it is even worst
- too much of too huge loaded "Map items" - check last tab of "Data manager". Some KML maps should be really huge and may slow down whole app
- also a used map may have difference - Vector maps (LoMaps and others) and usually little bit slower, mainly on older devices
- clearing a cache should make no difference
If such information worth it to be in FAQ, it's on @Michal. Hope this helps to find a reason of slowdown. Let me know.
EDIT: ah one more note. It may happen that in app (app itself or some problem with data) occur some error. This error if happen really often, generate some log and this creating of log may slow down really a lot if happen often. If none above helps, you may try to create a log and I'll check it. Thanks
Hi guys,
generally there is a few CPU consumers, that worth it to check:
- extra map layers - Map Overlays, WMS maps
- too much points and tracks - every device has own limits, so there are no exact numbers I may say, that since that Locus starts to be slower. I usually often use in "Data manager" > Points/Tracks tab > top button "Deselect all", which hide all points and in second tab also tracks in Locus that comes from database
- in case of geocaches, this limit is little bit lower as they are more complicated to draw on a map. Visible waypoints slow down also a little more then common points. In case of custom icons for geocaching, it is even worst
- too much of too huge loaded "Map items" - check last tab of "Data manager". Some KML maps should be really huge and may slow down whole app
- also a used map may have difference - Vector maps (LoMaps and others) and usually little bit slower, mainly on older devices
- clearing a cache should make no difference
If such information worth it to be in FAQ, it's on @Michal. Hope this helps to find a reason of slowdown. Let me know.
EDIT: ah one more note. It may happen that in app (app itself or some problem with data) occur some error. This error if happen really often, generate some log and this creating of log may slow down really a lot if happen often. If none above helps, you may try to create a log and I'll check it. Thanks
Replies have been locked on this page!