New Library has varying performance, sometimes very slow
In Progress
Opening the new My Library of 4.28 is sometimes very slow, maybe 10 seconds, while it's fast in other tries, less than 1 second. Both happens in the same Locus session, so no task switching or the like is involved. Also, no background task like navigation or the like, just sitting on couch and trying + learning new Library. Any idea how to tackle it down?
The same problem 
Hello Georg,
this happens only for the first time you open it?
Also, what exactly does mean "slow"? Do you see a long loading progress even if the folder does not contain a lot of points/tracks or the slowness means something different?
Hello Georg,
this happens only for the first time you open it?
Also, what exactly does mean "slow"? Do you see a long loading progress even if the folder does not contain a lot of points/tracks or the slowness means something different?
Hi Menion,
1st point needs further observation.
2nd point: Yes. I had only the 2 default folders points & tracks, now I have 4 folders.
Hi Menion,
1st point needs further observation.
2nd point: Yes. I had only the 2 default folders points & tracks, now I have 4 folders.
Thanks.
These problems will be hard to find and solve. I think that probably the best is to find the right moment when this happens and then describe it or provide backup of the database for testing. I see no other simple option unfortunately, sorry.
Anyway, the difference 1 or 10 seconds for the same folder is really big and should not happen in any case.
Thanks.
These problems will be hard to find and solve. I think that probably the best is to find the right moment when this happens and then describe it or provide backup of the database for testing. I see no other simple option unfortunately, sorry.
Anyway, the difference 1 or 10 seconds for the same folder is really big and should not happen in any case.
I had a similar behavior here. It took good 10 seconds to load and today just one second. Not sure if it first needed a full cloud sync.
BUT when it's started, the new database is so awesome quick I can't believe it's true. This was one of the best updates for locus ever to handle my big database.
I had a similar behavior here. It took good 10 seconds to load and today just one second. Not sure if it first needed a full cloud sync.
BUT when it's started, the new database is so awesome quick I can't believe it's true. This was one of the best updates for locus ever to handle my big database.
I do not know what happened on your devices guys, sorry. Loading from the database may be blocked if sync is running in the background. Anyway, most of the synchronizations should be really fast.
Give it some time, watch and maybe a repeatable situation will appear. App does not crash because of it, so it is not a critical issue that needs to be solved today. Work on the new "My library" is not ending, so there will be a lot of time to improve it.
And glad you like it. There are hundreds of hours on our side and many beta testers on the forum, so I believe it is a solid, stable and functional replacement of the old system. And for me as a developer it has a huge benefit. It is modern and a lot easier to extend than the old solution.
I do not know what happened on your devices guys, sorry. Loading from the database may be blocked if sync is running in the background. Anyway, most of the synchronizations should be really fast.
Give it some time, watch and maybe a repeatable situation will appear. App does not crash because of it, so it is not a critical issue that needs to be solved today. Work on the new "My library" is not ending, so there will be a lot of time to improve it.
And glad you like it. There are hundreds of hours on our side and many beta testers on the forum, so I believe it is a solid, stable and functional replacement of the old system. And for me as a developer it has a huge benefit. It is modern and a lot easier to extend than the old solution.
FYI, I never activated could sync, so sync blocking the DB can't be the reason for the delay.
FYI, I never activated could sync, so sync blocking the DB can't be the reason for the delay.
I have the same problem. There does not seem to be much regularity. I have about 20k tracks and points each. Sometimes, opening the library is instant. Sometimes it takes several seconds, I would say at most ten, probably less, like five. It shows "Loading" display. It does not only happen when opening the library, sometimes it also happens when changind folders, I think. It seems really random. It does not seem to be related to the size of the folder - when i enter a folder with 7 thousand points/tracks, it takes reliably about a second, which is ok, it is a lot of files.
I think this does not need to be a cold start. I think cold start after a phone restart tends to do this, but not always. Closing the app and opening it does not. I also reported it with several other things here: https://help.locusmap.eu/topic/37094-ui-regresions-with-new-folder-structure but there is no more info than I wrote here.
I have the same problem. There does not seem to be much regularity. I have about 20k tracks and points each. Sometimes, opening the library is instant. Sometimes it takes several seconds, I would say at most ten, probably less, like five. It shows "Loading" display. It does not only happen when opening the library, sometimes it also happens when changind folders, I think. It seems really random. It does not seem to be related to the size of the folder - when i enter a folder with 7 thousand points/tracks, it takes reliably about a second, which is ok, it is a lot of files.
I think this does not need to be a cold start. I think cold start after a phone restart tends to do this, but not always. Closing the app and opening it does not. I also reported it with several other things here: https://help.locusmap.eu/topic/37094-ui-regresions-with-new-folder-structure but there is no more info than I wrote here.
I have seen such across different apps. And my suspicion is that this has to do with Android / Java garbage collection / memory allocation.
I did not try to systematically look into free memory before action, though.
I have seen such across different apps. And my suspicion is that this has to do with Android / Java garbage collection / memory allocation.
I did not try to systematically look into free memory before action, though.
I've observed the same thing. But not always. And only since My Library
I've observed the same thing. But not always. And only since My Library
Replies have been locked on this page!