B6 Install Experience
I had 2 downloads, one right after the other. I am assuming the first was B6 and the second was resources.
After downloading, indexing started... it said indexing with 1 resource left... less than 5 minutes (3:55 minutes to be exact) and all was done.... guessing that this is the new indexing... only indexing what has not been previously indexed. No need to background index with that one 
If not... something went wrong. Looking at the indexing log all looks like it was done!!!! Woo Hooo!
attached log all the same.
Jim
Comments
-
I had 2 downloads, one right after the other. I am assuming the first was B6 and the second was resources.
After downloading, indexing started... it said indexing with 1 resource left... less than 5 minutes (3:55 minutes to be exact) and all was done.... guessing that this is the new indexing... only indexing what has not been previously indexed. No need to background index with that one
If not... something went wrong. Looking at the indexing log all looks like it was done!!!! Woo Hooo!
attached log all the same.
Jim
After a slight hickup I was up and running too. Beta 6 seems to be a giant leap forward as far as performance goes. From my brief time with it, even with it indexing my library (mine is doing the whole thing, probably because of the hickup) the program is far more responsive.
0 -
attached log all the same.
Hi Jim,
Thanks for the log. Beta 6 detected that 7 resources had been changed/added, and re-indexed just those seven. (The longest was LOGOSNA27INT, at 3:30; the others finished pretty quickly, which is probably why you only saw "1 resource remaining".) Results from the new index should be integrated directly into the application wherever possible; the one exception is searching the entire library by rank where the results will be split into two sections. Please let us know if you have any problems searching in Beta 6.
0 -
Seems to work as stated... two sections appear with search of entire library. First section is "New Resources" and the second section is "Library Results."
That seems to work. I will be getting my prepub NICOT/NICNT this week... I am guessing that they will be be indexed with the other "New Resources" or will this force a total re-indexing? What will trigger a total reindexing of "New" and "Old" resources? Other than the option at the top of the search window.
Jim
0 -
That seems to work. I will be getting my prepub NICOT/NICNT this week... I am guessing that they will be be indexed with the other "New Resources" or will this force a total re-indexing? What will trigger a total reindexing of "New" and "Old" resources? Other than the option at the top of the search window.
In Beta 6, the main index will be rebuilt if 25% of the resources are in the supplemental index. (I'm guessing that NICOT/NICNT probably won't push you over this limit.)
We're discussing options for the future, such as: changing the percentage (to something other than 25%); reindexing after some time has passed (e.g., four weeks, when the resources aren't "New" anymore); starting low priority reindexing immediately; making it manual-only; some combination of the above; etc.
0 -
I dont get why you would need to reindex whole library ever again (excepting a fresh install), surely the tables structures are the same, so you could surely just merge the records from the new index into the master index...
If you are going to have to reindex the whole thing again, then manual would be my current choice..
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
We're discussing options for the future, such as: changing the percentage (to something other than 25%); reindexing after some time has passed (e.g., four weeks, when the resources aren't "New" anymore); starting low priority reindexing immediately; making it manual-only; some combination of the above; etc.
I think it would be great to offer an option to 'optimize' the index -- especially if this could be done through the Windows Task Scheduler.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I dont get why you would need to reindex whole library ever again (excepting a fresh install), surely the tables structures are the same, so you could surely just merge the records from the new index into the master index...
If you are going to have to reindex the whole thing again, then manual would be my current choice..
Merging two indexes together is definitely a feature we want to add to the indexer; while not terribly difficult, we expect it to take sufficiently long (including testing) that it will be in a release after 4.0. For now, we anticipate shipping with the code that creates a supplemental index, and the only "merging" to be via rebuilding the main index from scratch.
0 -
we expect it to take sufficiently long (including testing) that it will be in a release after 4.0.
I guess I'll just have to be patient then..., but you are heading in the right direction as far as I am concerned...
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0
