L8 BUG/PERFORMANCE: Library sort took a huge amount of time
After downloading new/updated resources, while Logos was still indexing, I switched back to the floating Library window and clicked on the Last Updated field to sort by that column. Then I sat and waited.
It was taking such a long time that I went downstairs and had something to eat and came back up a few minutes later. It was still doing the spinning "busy" thing where the app is not responsive.
I finally couldn't stand the wait and switched away (Alt+Tab) to start typing this bug report, then switched back and it had finished sorting (though indexing was still in progress). I closed Logos almost immediately after this.
Log attached. (I waited until after Indexing finished to attach LogosIndexer.log.)
I am pretty sure the moment I activated my Library before clicking to sort by Last Updated was 00:24:51.2096 in the above logos.log file. After that point there are a lot of SQLite lines that seem to take more than 10 or more than 20 or even more than 30 seconds. I'm attributing the waiting around I had to do to how long all these things were taking.
So from starting to sort until it finally finished and I shut down Logos was about 8 minutes. (I suspect it would have gone on longer if I hadn't Alt+Tabbed away and back.)
Comments
-
Rosie,
I think this might be a case where a proc dump will be more helpful than logs. I would expect some performance issues when trying to sort the library while the application is still indexing. But it would be helpful to get some more info.
- Can you confirm if you get the same behavior when the app is not indexing?
- Also how is performance with 8.5?
- If this does reproduce would you be able to grab a proc dump?
If you are able to reproduce this and willing to get a proc dump please message me on Faithlife.com and I can give you an email address you can send the proc dump since the file is normally too large to updload to the forums. If you need help in getting a proc dump you can message me and I can email instructions or you can contact CS to help walk you through it.
Thanks,
Philana
0 -
I have not seen this problem when not indexing. I would expect indexing to be bumped down in priority when the user interacts with the application so that some semblance of responsiveness to user-requested actions can be maintained. Yes, I know I can pause Indexing for 4 hours if the app is running slowly. But I would want it to continue indexing, only at a slower pace because it's not a high priority thread, just working away in the background during idle cycles when I'm reading stuff on the screen, for example.
I have not been using the beta so I can't try it on 8.5. [EDIT: Ah, I see it's just shipped now, so I can update to it and try again and let you know.]
How does one grab a proc dump?
0 -
I couldn't reproduce it in 8.5.
0 -
HI Rosie,
I'm glad things are working so far. If you do have this issue come up again, instead of doing a proc dump if you could used the Logos Windows Profiler Utility to get a sample. Here are the instructions https://wiki.logos.com/Logos_Windows_Profiler_Utility.
Thanks,
Philana
0
