BUG: 4.0cR4: Massive adverse performance of MyTag field

I added a number of tags to many of my resources, into the "My Tags" field.

(I wanted a tag that would perform better than * or ratings:>=0 so tried "zz".)

After doing so, clicking "All Bibles" in a Search, to select an alternative range, took some 5-7 seconds. It also included under the Collections portion, an entry for "MyTag:zz" which is one of the entries in "My Tags" I was attempting to use.

I deleted some of my lesser or unneeded Collections, with no change. Still about 5+ seconds.

I deleted all data in "My Tags" except for maybe 100 resources where its too important to delete, and performance returned to 1 second for the dropdown in the graphic below.

My claim is that adding more than a few hundred or so values to "MyTags" appears to be unusable as currently implemented by the plumbing and database structures within Logos4.

Find more posts tagged with

Comments

MJ. Smith

My claim is that adding more than a few hundred or so values to "MyTags" appears to be unusable as currently implemented by the plumbing and database structures within Logos4.

Interesting - time to break out the SQLite browser and discover why.

JimTowler

https://community.logos.com/discussion/comment/130207#Comment_130207

Interesting - time to break out the SQLite browser and discover why.

My guess is that all the "My Tags" data for a single resource is stored in a single cell in the database for the library. It would use some kind of field-seperator, so the "click" I describe above would need to extract and break the data on that seperator and then process it.

It seems it also attempts to automatically create what might be useful collections, as it offered one based on "mytags:zz" even though I never created such a Collection. So, it wasted 5+ seconds making a Collection I never asked for and don't need, in an attempt to be helful I guess. It would be fine if it completed in the blink of an eye, but 5+ seconds is too long, for something I never ordered.

I really don't think MyTags as currently implemented is up to the task, given Logos4 is already using it automatically in some contexts to auto-create Collections. Its too overloaded. Too many uses for a single field.

MJ. Smith

https://community.logos.com/discussion/comment/130218#Comment_130218

My guess is that all the "My Tags" data for a single resource is stored in a single cell in the database for the library. It would use some kind of field-seperator, so the "click" I describe above would need to extract and break the data on that seperator and then process it.

Likely - but in the mid-70's a stack machine (Reality) had excellent performance with multiple values in a single field i.e. similar to what you assume but in a stack environment. So if Logos has a poor implementation, it's a known problem with a known algorithm so it should be quickly repairable.

Melissa Snyder

Service Release (SR) 1 will for 4.0c, which will be available soon, will include a fix for a bug that caused the Search panel to hang when choosing a large collection. This may resolve the problem you're seeing, too, however, I will test the latest build on my system using your example and report this additional problem if necessary. Thanks.

Update: I should add that choosing a Bible version from the resource selector drop-down in Search panel will be quicker in 4.0d Beta 1. Top Bibles, All Bibles, and Open Bibles will be available right away.

Update 2: I've tested this in the latest test builds of 4.0c and 4.0d Beta 1 on my system and found that the program did not hang, so I assume that 4.0c SR-1 will resolve this for you. (I don't have a release date for SR-1 or 4.0d B1 at this time.)

Todd Phillips

https://community.logos.com/discussion/comment/130389#Comment_130389

(I don't have a release date for SR-1 or 4.0d B1 at this time.)

So I'll assume I should stop checking today. [:'(]

JimTowler

https://community.logos.com/discussion/comment/130389#Comment_130389

Update: I should add that choosing a Bible version from the resource selector drop-down in Search panel will be quicker in 4.0d Beta 1. Top Bibles, All Bibles, and Open Bibles will be available right away.

Update 2: I've tested this in the latest test builds of 4.0c and 4.0d Beta 1 on my system and found that the program did not hang, so I assume that 4.0c SR-1 will resolve this for you. (I don't have a release date for SR-1 or 4.0d B1 at this time.)

Thanks Melissa.

I'll try and remember to recreate the delay on my system, once the update is released. Then I can confirm if its been addressed.

My resource set is around 1,300 at present. I know some here have many more, so its important the developers test that new features scale well to large libraries, many collections, lots of "My Tags" etc ...