Why does this menu take a long time to populate?

Wyy does my Bible menu (in the Bible search tab) take a long time to populate?:

Logos is not indexing, and I restarted the program just to be sure. It still sits and churns on this menu, and I haven't seen it finish yet. Thanks for any suggestions I might can do to my laptop to make this go faster (which is a brand new laptop, by the way.).

Comments

Sort by:
1 - 2 of 21

    Well the menu finally displayed, and I can begin to see why: there are over 300 items in this menu. Is there a way I can control what displays?

    Well the menu finally displayed, and I can begin to see why: there are over 300 items in this menu. Is there a way I can control what displays?

    No way to control what displays, but here's a why to bypass having to drop down that menu very often at all: For the two most common Bible versions that I like to search in, I've created shortcuts in my Favorites so that I don't have to wait for that menu to populate each time. Once you've selected the Bible version you want to search in, drag the Search tab into a Favorites folder, then right click on the name of what you dragged there and select Rename so you can title it something like "Search NRSV"

    image

    A helpful tip, this one, Rosie. Many thanks!

    Well the menu finally displayed, and I can begin to see why: there are over 300 items in this menu. Is there a way I can control what displays?

    You can control the number of collections with bibles in them, the number of bible resources you have tagged, and finally you can control the number of bibles that will show by hiding the ones you don't use, particularly Targums and TENTGM manuscripts.

    Dave
    ===

    Windows 11 & Android 13

    It's slow for me too, and I have a mongo machine with amazing specs. This has always annoyed me since L4 days, and L5 hasn't improved on it any.

    I wonder if it's on Development's radar to do something about the performance of this.

    It's slow for me too, and I have a mongo machine with amazing specs. This has always annoyed me since L4 days, and L5 hasn't improved on it any.

    I wonder if it's on Development's radar to do something about the performance of this.


    The root cause, however, is a meta data issue: a brick is not a house, a leaf of paper is no library and thus manuscript page 1234 is no bible and shouldn't be datatype bible but something else. Twenty real bibles would populate the menu much faster than several hundred mislabeled non-bibles.

    Have joy in the Lord! Smile

    The root cause, however, is a meta data issue: a brick is not a house, a leaf of paper is no library and thus manuscript page 1234 is no bible and shouldn't be datatype bible but something else. Twenty real bibles would populate the menu much faster than several hundred mislabeled non-bibles.
    I tried to see how long it would take for me and was at first pleasantly surprised that it took less than a second to populate the bibles I have. Then I realized that i don't have "over 300 items" in this menu so I was wondering if my logos is missing something. Well, I figuered it must be that others have so many bibles and collections of bibles to populate it. Wow I thought. Now that you've clarified it for me I remembered that - warning you might gasp in horror - I've hidden my manuscripts. It makes sense now so thanks for that.

    Now that you've clarified it for me I remembered that - warning you might gasp in horror - I've hidden my manuscripts.

    Dave already said that doing this will "control the number of bibles". I still see hiding lots of resources not as something I like to do (doing so is fast now, but un-doing it still seems to be painful) - but I was tempted.... I have a collection called "real bibles" for search purposes

    Have joy in the Lord! Smile

    I wonder if it's on Development's radar to do something about the performance of this.

    You should see a performance increase for this in the next beta version.

    I wonder if it's on Development's radar to do something about the performance of this.

    You should see a performance increase for this in the next beta version.

    [Y]

    You should see a performance increase for this in the next beta version.

    Well thank you, Bradley!

    I wonder if it's on Development's radar to do something about the performance of this.

    You should see a performance increase for this in the next beta version.

    Excellent news[Y]

    Thanks Bradley