4.2a Beta 4: Bible versions dropdown in Bible Search tab exceedingly slow

Rosie Perera

I switched to the Search tab (Basic search was selected already)

Clicked in the resources dropdown and typed kjv.

Waited while it populated the list with resources that matched that string. It wasn't that long a wait.

I ran a search.

Later came back to the Search tab and switched to Bible search.

Clicked in the resources dropdown and typed kjv.

This time it took nearly 2 minutes to populate the dropdown.

It is much slower doing this in the Bible tab than in the Basic tab for some unknown reason.

Log attached: 6253.Slow20110115.zip

This vast speed difference is consistently reproducible both several times in the same session, and in a new session, regardless of which order I try them in. Filtering the Bibles dropdown is always much, much slower.

Find more posts tagged with

Comments

Melissa Snyder

I can't reproduce with only the search panel open. Initially it took 2-3 secs for the Bible search drop-down, but afterward it was immediate, just like the Basic search. We'll review your log.

Edit: I asked a developer to review the log because during the 2 minutes it took for the drop-down to be populated on your system, there were several LibraryCatalogIndex entries, and I wasn't sure if they were the cause of the delay. He said it appeared that the search panel was evaluating all of your collections, and that one of your Collections had the filter "*." He recommended deleting that Collection to see if performance improves. The Collection searches should be cached, and filtering become faster the second and subsequent times.

Rosie Perera

https://community.logos.com/discussion/comment/212958#Comment_212958

Edit: I asked a developer to review the log because during the 2 minutes it took for the drop-down to be populated on your system, there were several LibraryCatalogIndex entries, and I wasn't sure if they were the cause of the delay. He said it appeared that the search panel was evaluating all of your collections, and that one of your Collections had the filter "*." He recommended deleting that Collection to see if performance improves. The Collection searches should be cached, and filtering become faster the second and subsequent times.

1) It would be odd that having a collection with the filter "*" should affect only the dropdown in the Bible tab, but not the same dropdown in the Basic tab.

2) I have a collection with that filter, as it's my "Entire Library" collection which I use whenever I want to export a listing of my whole library (until such time as it's possible to do that directly from the Library). So I don't really want to delete it permanently.

3) I did try deleting the "*" collection, and it didn't make any difference. Still exceedingly slow to drop down the list, only in the Bible tab.

4) Caching doesn't make any difference. Every subsequent time I try dropping down the list, it is still really, really slow to populate.

Let me know if you want more logs, with me trying it multiple times in one session, without the "*" collection, or whatever.

Dave Hooton

https://community.logos.com/discussion/comment/213123#Comment_213123

I have a collection with that filter, as it's my "Entire Library" collection

rating:>=0 is much faster!

Melissa Snyder

https://community.logos.com/discussion/comment/213123#Comment_213123

Let me know if you want more logs, with me trying it multiple times in one session, without the "*" collection, or whatever.

Could you provide a log without that collection and with no other panels open other than the Search panel?

Rosie Perera

https://community.logos.com/discussion/comment/213328#Comment_213328

Let me know if you want more logs, with me trying it multiple times in one session, without the "*" collection, or whatever.

Could you provide a log without that collection and with no other panels open other than the Search panel?

OK, here you go, stripped down reproducible case. Only the search panel is open, and that "*" collection was deleted before I even started this session up.

4276.Slow20110118.zip

It takes about 11 seconds to populate the list when I type kjv into the search box in the drop-down list in a Basic search tab and about 42-45 seconds (I had no second hand and counted aloud, so not very accurate) when I do it in a Bible search. Why it should be so much slower in the latter case is what I'm interested in, since those drop-downs ought to be using the same code.

Also interesting is why it should have to be "Searching for all records matching: ..." for every one of my many collections, just to populate the drop-down list. That is taking a total of about 14 seconds, which seems to me to be time spent unnecessarily. I guess it has to tell whether any Bibles are in each of those collections before it shows that collection name in the list. But this is grossly inefficient. That info should be cached ahead of time, as it's going to be the same every time I drop down the list (unless I've edited some collections). And yet Logos seems to be recomputing it each time. It also seems not to matter whether I've typed kjv into the dropdown's filter box or not. Dropping down the list in the Bible panel is really slow even with no filtering. Here's another log file to show that experiment: 4705.Slow20110118b.zip

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/213439#Comment_213439

That info should be cached ahead of time, as it's going to be the same every time I drop down the list (unless I've edited some collections).

When? (Should we make startup 14s slower?)

And yet Logos seems to be recomputing it each time.

Doesn't appear to be, to me. For example, "Searching for all records matching: nicot OR nicnt" only occurs once in the log, not multiple times. (Assuming that you performed multiple searches for "kjv" and not just one.)

Anyway, the results of these searches are calculated on demand, and cached. (Which I think is what you want Logos 4 to do.)

Rosie Perera

https://community.logos.com/discussion/comment/213443#Comment_213443

Anyway, the results of these searches are calculated on demand, and cached. (Which I think is what you want Logos 4 to do.)

14 seconds isn't that big a deal (and I do have lots of collections so I guess I need to be willing to take the hit). So it must be something else that is taking the bulk of the 45 seconds that it takes to populate that dropdown list for me. It's that slow each time. The caching doesn't seem to help.

And no, I wouldn't prefer that you do that caching at startup. But grab some time when Logos is idling with no user input, and do some housekeeping work like that. It will make the dropdowns faster. And if I'm really an eager beaver and get right to it immediately after booting Logos, why then you'll do the work on demand, which is just what you're doing currently.

Also, if I click on All Bibles and immediately type in kjv to filter the list, Logos shouldn't bother finishing computing the collection contents, since they aren't going to show up in the dropdown anyway. It should only be looking for collections that have kjv in their title.

I find it interesting/useful to be using Logos on a somewhat slow machine because I can find where the inefficiencies are this way and help you find areas that need to be performance tweaked. You might not even have any noticeable delay at all on your machine when you type kjv in the All Bibles dropdown filter.