B11 - Very slow to list parallel resources

I haven't used the parallel resources button (the little vertical bars button) much until I recently discovered its utility. However the time taken to "find" parallel resources is (imho) excessive. Sometimes it takes more than 5 seconds to "search" while the spinning wheel thingy spins.

Any chance this can be optimized, as it is very useful (now that I've discovered its value) :-)

Find more posts tagged with

Comments

Jack Caviness

Any chance this can be optimized, as it is very useful (now that I've discovered its value) :-)

This must be a problem in the core code, for the same complaint surfaces frequently for the Windows version. The system rebuilds the list(s) each time you click the parallel resources button.

Stuart Robertson

https://community.logos.com/discussion/comment/170794#Comment_170794

So does that mean the case for optimizing this is twice as strong? :-) ... since both "camps" would benefit and it is a complaint that "surfaces frequently".

Jack Caviness

https://community.logos.com/discussion/comment/170876#Comment_170876

So does that mean the case for optimizing this is twice as strong? :-) ... since both "camps" would benefit and it is a complaint that "surfaces frequently".

Hopefully, this will be fixed soon, but I have not seen any response from Logos.

Stephen Ashton

https://community.logos.com/discussion/comment/170794#Comment_170794

The system rebuilds the list(s) each time you click the parallel resources button.

This is a prime example of something that should be cached by Logos 4 to speed up display.

Russ Quinn

https://community.logos.com/discussion/comment/171140#Comment_171140

This is still a problem in the Gold Release.

My parallel resource lists takes around 30 seconds to populate.

Dewayne Davis

https://community.logos.com/discussion/comment/171140#Comment_171140

The system rebuilds the list(s) each time you click the parallel resources button.

This is a prime example of something that should be cached by Logos 4 to speed up display.

I'm not sure, but I think the reason for the delay is that L4 is actually only showing the parallel resources for the specific verse location. Libronix didn't do this an it was frustrating to move to a parallel resource that didn't cover the current location.