Bug: Slow datatype lookup for resources not in prioritisation list

Page 1 of 1 (3 items)
This post has 2 Replies | 0 Followers

Posts 13423
Mark Barnes | Forum Activity | Posted: Sat, Jun 11 2011 3:58 AM | Locked

It was pointed out in another thread that adding resources to the prioritization list can speed Logos up. That;s quite understandable when there are hundreds or thousands of resources that support a particular datatype, but it shouldn't be, when there is only one. This seems to point to a bug. (Apologies if I've misunderstood the process and there's a good reason for this behaviour.)

A great example is the Lexham High Definition New Testament. It has loads of pop ups, which are all tagged with the Lexham High Definition New Testament Glossary datatype. There is only one resource that can open from this datatype. So regardless of prioritisation, Logos should simply search for the 'hdnt' datatype in keylinking.db, discover there's only one resource, and go straight to its mstidx file. Instead, it wastes about 2 seconds doing endless searching of catalog.db. 2 seconds might not seem very much, but you often need multiple lookups,and the 2 seconds quickly add up.

If you add the Glossary into the prioritisation list, it speeds things up considerably. This should not be.

Posts 13423
Mark Barnes | Forum Activity | Replied: Fri, Jun 17 2011 1:35 AM | Locked


Posts 4077
Melissa Snyder | Forum Activity | Replied: Mon, Jun 20 2011 2:53 PM | Locked

I've submitted your report to development.

Update:  You should see an improvement in the next beta.

Page 1 of 1 (3 items) | RSS