Bug: Logos 4 resource hogging

I am posting this as a bug because this far into the development of Logos 4, it can no longer be ascribed to beta stages. Stable versions have come and gone and though there have been improvements, Logos 4 continues to make capable computers sweat too much.

The "not responding" experience still is a far too common occurrence. I am sure that I don't have the most powerful computer that can be had on the market now, but I think a T6500 (intel core duo) with 4 GB of fast ram and other more than decent hardware should be sufficient not to cough when using Logos 4 and opening several windows within it.

But such is not the case. I have Outlook opened and Chrome and Logos 4. I had one commentary opened, the NASB, one guide and one note file. The software froze. It frequently does in this kind of situation and yet being able to have resources and tools side by side is precisely part of what is so useful in Logos 4. I hear my fan go on and stay on when I start a guide or a search or open a note file. 

So it seems to me, as a user not as having knowledge of programming, that the "engine" of Logos 4 was from the start and by and large remains cumbersome in that capacity. I read of other softwares that experience this kind of problem and then they come up with a new version where they completely rewrite the code, experiencing significant performance improvement by changes under the hood rather than in the functionalities. Here is another way to put it: Logos still feels the way Windows Vista did: worked but there were problems. It'd be great to work on the "Windows 7" experience equivalent instead.

Is this already in the plans?

PS: I wonder also whether the beta user addiction helps promote moving Logos 4 in the direction of stability (doing well what it already does) as opposed to looking for new toys (ie, new "exciting" features)...

Comments

Sort by:
1 - 2 of 21

    PS: I wonder also whether the beta user addiction helps promote moving Logos 4 in the direction of stability (doing well what it already does) as opposed to looking for new toys (ie, new "exciting" features)...

    You're probably right (I'm assuming your rhetorical question implied that the answer was "no, the reverse"). Guilty as charged.

    The things that I still find way too slow and annoying are dropping down a menu that has a dynamically generated list of resources (e.g., the "Search In" menu for Bible Search, and the left side of the right-click menu when you right-click on a single word). I get the spinning "wait" icon in those instances and it takes many seconds to finish. Unacceptable. The UI should have a really snappy feel, and dropdown menus should all appear virtually instantaneously. And I've got a mongo fast machine with a NovaBench score of 1772 (compared to my old laptop which had a score of 197 but still ran Logos)!

    Also, updating the library catalog after making a change to tags or a resource name is too slow ("Updating library catalog. List may be incomplete" message appears for 10-15 seconds).

    And I get the frozen screen and "Not responding" for 20 seconds or more when I open a medium-sized somewhat complex clippings file (made up of one clipping for each of the tables of contents from the Early Church Fathers volumes, complete with their links) or try to scroll in it past a juncture between clippings. Ditto when I do "close all" when there are a lot of tabs open.

    Logos has taken the approach that when people complain in general about speed, they say "we can't do anything about it unless you tell us precisely what action is taking too long for you and send us your log file from doing that action." They do respond with improved performance when we do that, which is good. But I wish they were more proactive about it internally. I'm not sure how many of them are actually using Logos on a day-to-day basis as much as we are, so they might not notice and be frustrated by these things like we are. They see it from under the hood, and spend so much of their time coding and fixing bugs that it must leave little time for actual Bible study using the product. And the ones who are using it extensively as a study platform and would like to work on performance improvement (or fixing annoying little bugs that have been around for several versions) are prevented from doing so by other stuff on their task list that is more important to management.

    The UI should have a really snappy feel, and dropdown menus should all appear virtually instantaneously. And I've got a mongo fast machine with a NovaBench score of 1772 (compared to my old laptop which had a score of 197 but still ran Logos)!

    Yikes, Rosie!  Thanks for sharing-- what a computer you do have and if you say Logos is not snappy on it, I think I will give up and settle for mediocrity.    [:'(]

    I think I will give up and settle for mediocrity.  

    That is so sad. I hope we never stop pressuring them to make it better. Remember the parable of the persistent widow? (Luke 18:1-8)

    Rosie,

    I'm 60; I can leave the "fight" up to those of you who have the chutzpah.   [:)]

    The UI should have a really snappy feel, and dropdown menus should all appear virtually instantaneously.

    You can make your installation feel much snappier. Run L4 Mac for a day or two. [:D]

    The things that I still find way too slow and annoying are dropping down a menu that has a dynamically generated list of resources (e.g., the "Search In" menu for Bible Search, and the left side of the right-click menu when you right-click on a single word). I get the spinning "wait" icon in those instances and it takes many seconds to finish. Unacceptable. The UI should have a really snappy feel, and dropdown menus should all appear virtually instantaneously. And I've got a mongo fast machine with a NovaBench score of 1772 (compared to my old laptop which had a score of 197 but still ran Logos)!

    Also, updating the library catalog after making a change to tags or a resource name is too slow ("Updating library catalog. List may be incomplete" message appears for 10-15 seconds).

    And I get the frozen screen and "Not responding" for 20 seconds or more when I open a medium-sized somewhat complex clippings file (made up of one clipping for each of the tables of contents from the Early Church Fathers volumes, complete with their links) or try to scroll in it past a juncture between clippings. Ditto when I do "close all" when there are a lot of tabs open.

    WOW, this tells us a lot about L4, and it is not good.

    WOW, this tells us a lot about L4, and it is not good.

     

    Pete,

    that's just it....it doesn't.

     

    I have 1/2 the machine that Rosie does and I have no problems and no speed complaints.....

     

    That's only half of the story....the other half is that many users with less machine run just fine.....it's puzzling.

    Robert Pavich

    For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__

    WOW, this tells us a lot about L4, and it is not good.

     

    Pete,

    that's just it....it doesn't.

     

    I have 1/2 the machine that Rosie does and I have no problems and no speed complaints.....

     

    That's only half of the story....the other half is that many users with less machine run just fine.....it's puzzling.



    I disagree.  There is a real problem if Rosie's computer is having problems.  If L4 is the only program that displays this problem, then the problem is in L4.

    The things that I still find way too slow and annoying are dropping down a menu that has a dynamically generated list of resources (e.g., the "Search In" menu for Bible Search

    How many collections do you have?

    , and the left side of the right-click menu when you right-click on a single word).

    English words, Greek words, Hebrew words, any words? Is this a word found in a dictionary, or a typo? Can you give more specific examples?

    I get the spinning "wait" icon in those instances and it takes many seconds to finish. Unacceptable. The UI should have a really snappy feel, and dropdown menus should all appear virtually instantaneously.

    Let's assume that in order to show a list of dictionaries on the context menu for a word, we need to determine which dictionaries contain that word. (I would assume it's unacceptable to display incorrect and inappropriate destinations.)

    Determining these destinations (in a dynamic library) will require some amount of work to be done, whether it be looking the word up in a central DB or opening individual resources to check. Should drop-down menus not be allowed to perform any work, so that they can appear instantaneously? Should the menus be completely static, with the dynamic options replaced with commands that open new reports that do the equivalent work? (I.e., instead of listing dictionaries, hard-code a menu item that opens a report that loads the top 5+ KeyLink destinations.)

    We've chosen to minimize mouse clicks and movement, at the expense of having a menu that populates dynamically. That is, this is by design. [:)]

    Also, updating the library catalog after making a change to tags or a resource name is too slow ("Updating library catalog. List may be incomplete" message appears for 10-15 seconds).

    This probably isn't multithreaded, but it could be. (There are a lot more multi-core computers now than when we released the software.)

    And I get the frozen screen and "Not responding" for 20 seconds or more when I open a medium-sized somewhat complex clippings file (made up of one clipping for each of the tables of contents from the Early Church Fathers volumes, complete with their links) or try to scroll in it past a juncture between clippings. Ditto when I do "close all" when there are a lot of tabs open.

    I haven't tried to reproduce this yet, but I noticed you posted your file on another thread, so we may be able to look at this.

    One final thing: how many visual filters do you typically have enabled, and how many of them search for "*"? If you love to do that, just know that the system will not love you back... I would highly recommend disabling as many of those as you can.

    i know that you addressed Rosie, but not all users will have the same wishes.

    How many collections do you have?

    Perhaps in this case you could add a menu item (in the search menu [icon in the upper left] which would allow us to disable the use (similar to Cited By checkboxes) to limit which collections & tagged resources to use in our search.
    EDIT: i know that the key use of collections is for searching, but some collections i use primarily for PG. Also i have a large number of tagged resources of which only a few that i would want to search.

    We've chosen to minimize mouse clicks and movement, at the expense of having a menu that populates dynamically. That is, this is by design.

    i want to keep dynamic design so that i don't get resources which are not relevant. But for those with larger libraries or who are experiencing this issue, you could add an item in Program Settings to disable dynamic in which case it just gave them their top 5 resources (of which some would not have their word in them). EDIT: this could also work with PRs.

    One final thing: how many visual filters do you typically have enabled, and how many of them search for "*"? If you love to do that, just know that the system will not love you back... I would highly recommend disabling as many of those as you can.

     i keep most of my visual filters Off until i want to view them and even then selectively in specific resources. (EDIT: i do the same with much of my highlighting).  i do notice sluggishness when i have several resources linked and have Information and other tools up. It would be nice in Information if we could select On Hover or On Click for the information tool. i can do this on some of the other tools. This might speed up scrolling a little so that information tool isn't trying to populated as i move my mouse around. (oops, this ability is already there [:$] )

    QLinks, Bibl2, LLR, Macros
    Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1

    , and the left side of the right-click menu when you right-click on a single word).

    English words, Greek words, Hebrew words, any words? Is this a word found in a dictionary, or a typo? Can you give more specific examples?

    For a common word "the", the context menu populates quickly in EBC Intro and slowly in NET Bible & ESV bible.

    "a" populated quickly in EBC Intro but took over 2 min in NET Bible and ESV (1 Pe 5:1).

    image

    When looking at the generation in NET the last detail to be shown is Person Jesus. In ESV it is the items below Reference ie. Manuscript thru Person. I don't understand the relevance of Person Jesus for these words (the Elders & a Witness) so I would gladly sacrifice that "dynamic" element and have it apply to the specific noun when selected!

     

    Dave
    ===

    Windows 11 & Android 13

     

    For a common word "the", the context menu populates quickly in EBC Intro and slowly in NET Bible & ESV bible.

    I see the same. For example:

    I've just right-clicked on the word "the" in John1:1 in the ESV (the "the" in "the Word was with God") and it took 22 seconds for the right-side of the context menu to fully populate.

    Graham

    For a common word "the", the context menu populates quickly in EBC Intro and slowly in NET Bible & ESV bible.

    "a" populated quickly in EBC Intro but took over 2 min in NET Bible and ESV (1 Pe 5:1).

    This has been fixed in 4.3 Beta 4 - the menu now populates in about 1sec!

    Dave
    ===

    Windows 11 & Android 13

    The things that I still find way too slow and annoying are dropping down a menu that has a dynamically generated list of resources (e.g., the "Search In" menu for Bible Search

    How many collections do you have?

    Lots. I use them for all kinds of things (creating bibliographies, or at least making suggestions of resources on areas of interest of mine; helping me wrap my head around what-all is in my library; and structured browsing), rarely just for limiting searches. I have only a handful of collections that I use to restrict searches. The vast majority are not for that purpose. I have around 120 in all. I'm attaching a list of them.

    I am unhappy with the implication that I cannot have lots of collections if I want the Logos UI to feel snappy. You produce this powerful software and I love it and long to be a power user of it. Having lots of collections doesn't appear to me to be an unreasonable expectation. The more resources I buy from Logos the more collections I think of that I want to have. If that will be too hard for Logos to handle, maybe I ought to stop buying so many new resources... [;)]

    , and the left side of the right-click menu when you right-click on a single word).

    English words, Greek words, Hebrew words, any words? Is this a word found in a dictionary, or a typo? Can you give more specific examples?

    Lo and behold, this particular performance problem seems to have been fixed! It used to be with any word (English, Greek, Hebrew, and I'd usually be annoyed with it most when I was reporting typos, because I had to wait for the menu to populate before the Report Typo command would show up). But it was very snappy when I just tried it now. So thanks for fixing it, and sorry I hadn't noticed when that change occurred. It's been relatively recently, since 4.3 beta 1 or 2.

    I get the spinning "wait" icon in those instances and it takes many seconds to finish. Unacceptable. The UI should have a really snappy feel, and dropdown menus should all appear virtually instantaneously.

    Let's assume that in order to show a list of dictionaries on the context menu for a word, we need to determine which dictionaries contain that word. (I would assume it's unacceptable to display incorrect and inappropriate destinations.)

    Determining these destinations (in a dynamic library) will require some amount of work to be done, whether it be looking the word up in a central DB or opening individual resources to check. Should drop-down menus not be allowed to perform any work, so that they can appear instantaneously? Should the menus be completely static, with the dynamic options replaced with commands that open new reports that do the equivalent work? (I.e., instead of listing dictionaries, hard-code a menu item that opens a report that loads the top 5+ KeyLink destinations.)

    Totally understandable, and yet that is now fast enough for me. I'm still concerned about the "Search in" dropdown in Bible Search, though. Why would that be any more complicated to generate than the list of dictionaries in the context menu for a word? It takes on the order of 8 seconds to display, and all that's in that dropdown is a list of all my collections and series that have Bibles in them. Can't that info be cached -- to be updated whenever the user edits a collection definition or downloads new resources (relatively infrequent operations which one might expect to take a bit longer than menu dropdown, and which thus would hide the cost of generating this list)? It seems to be generated again every time I click that dropdown menu.

    Here's a log file from a session where I booted to an empty layout, opened a search panel to Bible search, and clicked the "Search in" dropdown: 36360.Logos4.log

    One particularly troubling gap of 6 seconds is accounted for by the SyncManager -- why does Logos need to be syncing while it's in the middle of displaying a dropdown list? Or am I misreading the log file?

    2011-04-22 17:08:06.0447    12    Info    SyncManager    (500ms) Downloading items.
    2011-04-22 17:08:12.2110    1    Info    IsWorkingControl    Hiding IsWorkingControl (name  id 53855148)

    We've chosen to minimize mouse clicks and movement, at the expense of having a menu that populates dynamically. That is, this is by design. Smile

    And it's a good interface design. I'm not complaining about the fact that the menu is dynamic, just about how long it takes to generate the contents of it (and again here, I'm no longer talking about the context menu, since that performance problem seems to be gone). I hope the "Search in" dropdown can be sped up.

    Also, updating the library catalog after making a change to tags or a resource name is too slow ("Updating library catalog. List may be incomplete" message appears for 10-15 seconds).

    This probably isn't multithreaded, but it could be. (There are a lot more multi-core computers now than when we released the software.)

    And I get the frozen screen and "Not responding" for 20 seconds or more when I open a medium-sized somewhat complex clippings file (made up of one clipping for each of the tables of contents from the Early Church Fathers volumes, complete with their links) or try to scroll in it past a juncture between clippings. Ditto when I do "close all" when there are a lot of tabs open.

    I haven't tried to reproduce this yet, but I noticed you posted your file on another thread, so we may be able to look at this.

    One final thing: how many visual filters do you typically have enabled, and how many of them search for "*"? If you love to do that, just know that the system will not love you back... I would highly recommend disabling as many of those as you can.

    I typically only have one visual filter enabled, if any. None of my visual filters search for "*". I have just turned them all off in all resources and restarted Logos and tried opening that clipping file again, and it didn't make any difference.

    The things that I still find way too slow and annoying are dropping down a menu that has a dynamically generated list of resources (e.g., the "Search In" menu for Bible Search

    How many collections do you have?

    Lots. I use them for all kinds of things (creating bibliographies, or at least making suggestions of resources on areas of interest of mine; helping me wrap my head around what-all is in my library; and structured browsing), rarely just for limiting searches. I have only a handful of collections that I use to restrict searches. The vast majority are not for that purpose. I have around 120 in all. I'm attaching a list of them.

    I forgot to post the list of all my collections -- it might be interesting for you to see how someone is using collections. Here it is:
    1031.All My Collections (as of 2011-04-22).doc

    Not sure if my input is helpful at this point compared to the heavy users with big libraries, but:

    How many collections do you have?

    54 collections for a library of 465 resources

    We've chosen to minimize mouse clicks and movement, at the expense of having a menu that populates dynamically. That is, this is by design.

    I love the dynamic menus, collections, etc and wouldn't prefer that functionality removed...but as suggested elsewhere, I would like to see some of these things pre-cached (on program startup?) and only refreshed when they are changed...especially things like collections that shouldn't change frequently, and certainly shouldn't change and need to be generated again 2 minutes after I last clicked on Parallel Resources (or whatever).

    One final thing: how many visual filters do you typically have enabled, and how many of them search for "*"? If you love to do that, just know that the system will not love you back... I would highly recommend disabling as many of those as you can.

    I currently only have one, simple visual filter and it is only enabled when I'm actually using it, which isn't very often.

     

    I don't see an easy way of counting the collections or capturing their titles. But I (partial) shot of my Passage Guide should make it clear how I use them.

    image

     

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

    I don't see an easy way of counting the collections or capturing their titles.

    I captured mine from the dropdown menu using the great little screen capture OCR utility called ABBYY Screenshot Reader ($10 - I use it literally every day; well worth it). They make it hard for you to find out how to get it. When you click Buy, after selecting your region, you are taken to another page that shows all the products again (as if you entice you to spend more) and you've got to scroll down to find Screenshot Reader. Or just go here to download the trial version (good for 15 days) and then upgrade it to the paid version if you like it.

    [Y]

    The fact that Rosie's experience (as far as mentioned times and delays) isn't significantly better than mine, despite her significantly faster computer*, points to the fact that there is still much room for performance optimization.

    *I have an Intel Core 2 Duo 3GHz, 8GB RAM, Intel G2 80GB SSD, Radeon 6790 (I think, not in front of it right now), and 64-bit Windows 7

    I am somewhat relieved to hear that I am not the only one who is still having this problem, and who is still not happy with performance with L4. 

    It's probably a bit easier to forgive Logos having lived through the days of floppies and dial up. My main issue is that I can't really open too much.

    The mind of man is the mill of God, not to grind chaff, but wheat. Thomas Manton | Study hard, for the well is deep, and our brains are shallow. Richard Baxter

    It's probably a bit easier to forgive Logos having lived through the days of floppies and dial up. My main issue is that I can't really open too much.

    Hey Michael, this is really funny: you need to look back to the day of floppies and dial up to feel better about Logos 4 performance issues! I love the point of reference.

     

    LOL

    Yes

    The fact that Rosie's experience (as far as mentioned times and delays) isn't significantly better than mine, despite her significantly faster computer*, points to the fact that there is still much room for performance optimization.

    *I have an Intel Core 2 Duo 3GHz, 8GB RAM, Intel G2 80GB SSD, Radeon 6790 (I think, not in front of it right now), and 64-bit Windows 7

     

    I think (and I've said this before) that this exact issue is puzzling to me. It's clearly NOT an apples and apples relationship with our machines and Logos...i.e. some users with Cray Supercomputers don't get significantly better performance that those with a 2 year old upper/middle of the road laptop....it just makes no sense...and really points to unknown factors rather than an "optimization" issue...(if we all ran that exact Laptop that runs L4 best we wouldn't be talking about it)

     

    My Dell Laptop is NOT the best on the block...nor is it new but it runs L4 very nicely....and so the fact that Rosie is having spinning pizzas during drop down menus just has me flummoxed...lol.

    I have an Intel Core 2 Duo 2.2 GHz, 6GB RAM, Dell HD (nothing special) , Radeon 4650  and 64-bit Windows 7

    And I get no spinning pizzas....

     

    Robert Pavich

    For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__

    My Dell Laptop is NOT the best on the block...nor is it new but it runs L4 very nicely....and so the fact that Rosie is having spinning pizzas during drop down menus just has me flummoxed...lol.

    I have an Intel Core 2 Duo 2.2 GHz, 6GB RAM, Dell HD (nothing special) , Radeon 4650  and 64-bit Windows 7

    And I get no spinning pizzas....

    Robert: are you saying that you can open say a passage guide, a note set or a search, a commentary, a Bible and switch back and forth with no slowdowns at all, no "spinning pizza"? 

    And if it is your blessed experience, then the question is begging: how many are in your boat vs. those who are not and more importantly, why might this be? 

    A couple questions come to mind: imported notes have been mentioned in connection with a number of problems: do you have any? Secondly, large note sets have also been noted as a potential source of problems: do you have any? Lastly, I wonder about whether the size of one's library (and index processing) is also a X factor. I have 1,738 resources. Is your library large? Just looking for answers. 

    Alternatively, perhaps Logos users could collect money to ship your laptop to Logos headquarters for investigation of the miracle computer. What makes your Logos 4 purr? Is it your desktop background? The music you play? The paint in your office?

    And if it is your blessed experience, then the question is begging: how many are in your boat vs. those who are not and more importantly, why might this be? 

    The only slow downs or delays that I get are during a Bible search as described here: http://community.logos.com/forums/p/32059/238663.aspx#238663

    I sent in a support request asking them to watch the video but after the generic "We got your request" email, no follow-up or anything.

    are you saying that you can open say a passage guide, a note set or a search, a commentary, a Bible and switch back and forth with no slowdowns at all, no "spinning pizza"? 

    Just tested it, along with a few more commentaries open and no slowdowns (spinning pizzas). Instead of a Bible search I done an entire library.

    imported notes have been mentioned in connection with a number of problems: do you have any?

    Just a few.

    Secondly, large note sets have also been noted as a potential source of problems: do you have any?

    Not nearly as large as I have heard others describe, so my answer would be no.

    Lastly, I wonder about whether the size of one's library

    1,417 books showing and several other language (Greek, Hebrew and Aramaic) resources hidden.

    I am on my Asus laptop at work right now and the processor is 2.4 GHz with 6 Gig RAM Windows 7 Home Premium 64 bit.

     

    Francis,

    I have an Core2 Duo T9400 @ 2.53 GHz. with 4GB of RAM, a ATI Mobile Radeon 512MB video card, and 7200RPM Drive.  For the most part I find it more than useable and never get spinning pizzas.  What does you have for video and hard drive?  Those are important too, maybe more so than CPU.

    I run a lot of stuff on my computer, and I find I need to manage memory myself.  I find that I need to keep memory in use to less than about 2.8G, otherwise everything (not just Logos) starts slowing down.  I find that Firefox and Logos are my largest contenders for memory and sometimes I need to restart one or the other to gain back needed memory (Firefox is the usual culprit).

    A couple questions come to mind: imported notes have been mentioned in connection with a number of problems: do you have any? Secondly, large note sets have also been noted as a potential source of problems: do you have any? Lastly, I wonder about whether the size of one's library (and index processing) is also a X factor. I have 1,738 resources. Is your library large? Just looking for answers. 

    I don't use large note files on purpose.  I've found that many notes in one file do slow things down.  As do many highlights in one resource.  Those two areas do need to be tweaked for performance.  However I don't think the number of resources affect general performance at all (I have over 2000).  All that a large library affects is start-up time (a bit) and indexing time (a lot).  I try not to use Logos while it's indexing because everything takes twice as long.  It's not unusable, but I'll pause indexing until I'm not using the computer because I need both the memory and CPU for interactive stuff.

    MacBook Pro (2019), ThinkPad E540

    Robert: are you saying that you can open say a passage guide, a note set or a search, a commentary, a Bible and switch back and forth with no slowdowns at all, no "spinning pizza"? 

     

    Yes

     

    A couple questions come to mind: imported notes have been mentioned in connection with a number of problems: do you have any?

     

    Nope

     

    Secondly, large note sets have also been noted as a potential source of problems: do you have any?

     

    Probably not large....I do have the content of some web pages in notes so some are large and some are not.

     

    Is your library large?

     

    1,095 with about 500 or so hidden.

     

    Alternatively, perhaps Logos users could collect money to ship your laptop to Logos headquarters for investigation of the miracle computer.

     

    It's not just me....the pattern has been random since the beginning....it's not just that a larger computer runs logos better....I've seen posts where a computer that is a LOT older and less powerful than mine running logos and then there was a guy (don't remember who) who had 12GB ram with an SSD and quad processors...and he was complaining about speed. (as I recall, I could be wrong)

     

    there doesn't seem to be a hard and fast rule....

    Robert Pavich

    For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__

    Perhaps someday, all the indexing and auto-populate activity will come from an outsourced Logos data center, where cloud computing will be extremely cheap in the coming years.   Only using local resources when Network.GetIsNetworkAvailable() is false.   

    I am actually considering buying this software, so a test drive would be nice.

    I think (and I've said this before) that this exact issue is puzzling to me. It's clearly NOT an apples and apples relationship with our machines and Logos.

    The change from a 4 yr old Core 2 duo 2.0 GHz with 2 GB memory & Win XP to an i5 2.53 GHz with 4 GB memory & Win 7 has not significantly improved my experience with L4, and it was acceptable with XP! Only Indexing & search speeds show a consistent improvement between my different machines.  I have 12 tabs in my Layout but don't experience issues with 15 - 16 tabs (I start to close them above this point).

    Significantly, I don't share Rosie's experience with lag on the context menu of my i5 using 4.2a SR-4.

    I don't use Notes/Handouts and my Clippings are modest (5 to 8 "medium" frames); so no performance issues there!

    Even if Logos can say they have optimized code across the board, I suspect  they will still be stuck with WPF & Video card/driver issues impacting lag + the random nature of garbage collection and JIT code generation in .NET ie. MS and NVidia/ATI code, though I expect the latter to improve their code (drivers) much sooner than the former.

    So my main issue is with persistent bugs, regression bugs (those fixed in an earlier release!) and a lack of functionality (not necessarily features) when compared with L3.

    Dave
    ===

    Windows 11 & Android 13