Okay, I will confess right from the start, I am totally ignorant of the technical aspects of indexing and what constraints it places on how it works in Logos in relation to other aspects of the software. I am simply speaking from the standpoint of experience: latest example Wiersbe's study guide on Revelation from Vyrso. We're talking a small book to start with and vyrso books as I understand it, are precisely NOT tagged as logos books are. Yet here it is a long indexing session during which my computer, which otherwise performs very well is annoyingly lagging. All this for this one little, untagged book? I turned it off at 15% so I could get some work done.
Sure, some will say, download later, pause indexing, change process prioritisation. There is something to be said for all this, but each of these workarounds have their disadvantages as well. And these are bandaids, they don't deal with the root problem.
I remember in Wordsearch -- I know, a considerably less complex piece of software -- that they would do incremental indexing. I was under the impression that this was the case, at least at some point, in Logos as well, and that one could rebuild or consolidate the index. But then if it is incremental, why so long for so little material and why does it use so much processing power?
Well, I know all this can be explained. That's not my point however. I don't want to be told that the reason my car is slow is because it is designed to work with square wheels; what I want to know is whether, really, we cannot revisit the design so as to use the much more efficient circular ones. I find it hard to imagine that there cannot be a better way.
BTW, performance has long been a problem with Logos, and one that comes back in the conversation with users of other competing software ("I used Logos in the past but it was so slow..."). The overall performance has improved a lot (speed of searches), but indexing is perhaps another relic of a problematic approach. This has been the case long before resources started to be super-tagged in relation to all kinds of datasets and types, so it's difficult to think this is the reason. I don't know, was it coded unpropitiously and now it is hard to change it?
