Logos indexer was reporting "one minute remaining" for five hours! Lots and lots of redundant lines like this:
2011-01-20 06:05:34.5615 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 957.5m2011-01-20 06:06:04.5745 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 958.0m2011-01-20 06:06:34.5875 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 958.5m2011-01-20 06:07:04.6005 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 959.0m2011-01-20 06:07:34.6125 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 959.5m2011-01-20 06:08:04.6255 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 960.0m2011-01-20 06:08:34.6385 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 960.5m2011-01-20 06:09:04.6515 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 961.0m2011-01-20 06:09:34.6645 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.01 * 0.00) after 961.5m2011-01-20 06:10:04.6775 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.02 * 0.00) after 962.0m2011-01-20 06:10:34.6905 9 Info WindowsIndexerProgress 1.0000 = 1 * (1.00 * 0.00 + 1.00 * 0.74 + 1.00 * 0.26 + 0.02 * 0.00) after 962.5m
This goes on for about four and a half hours with nothing else happening.
I finally got fed up with waiting and paused it and restarted it to see if that might jog something. I also close Logos at that time, in case it had been interfering somehow. The indexer kept going for another half hour (still reporting "one minute remaining" all along) and finally finished up.
The complete log which includes the pause and restart, as well as the Logos log file generated concurrently with the part up to the pause is here: 3683.OneMinuteRemaining.zip
How to Ask for Help | Logos Wiki | My Machine Specs | My Blog
I hope that's not what I have to look forward to. I've been bouncing between 3 and 4 hours for the last 24 hours, except for a little while this morning when it said something in the 20's.
https://www.mathdeft.com/
mine finished successfully in 22h53m
Never Deprive Anyone of Hope.. It Might Be ALL They Have
Jeffrey Glen Jackson:I hope that's not what I have to look forward to.
If you know that it takes a certain time to index then ignore the often wild predictions the program issues! My indexing time was slightly faster than 4.2!
Dave===
Windows 10 & Android 8
very true I was informed 110hrs at one point..
DominicM: very true I was informed 110hrs at one point..
If Logos will not remove the timing estimates then they should also state what is happening:-
Dave Hooton: If Logos will not remove the timing estimates then they should also state what is happening:- indexing 20/128 Bibles ... finished indexing Bibles, writing postings merging Bible indexes indexing 10/1218 in main Library ... finished indexing Library, writing postings merging Library indexes
I would find that much more useful and reassuring that something was happening. The timing estimates are bogus. Even if it just says something at the beginning like "this could take several hours; be patient" I'd be fine with that. Seeing that it has progressed to the next step of the indexing is much more valuable than seeing some random number jump all over the place. Or get stuck in one place for hours.
+1
I have just completed indexing for L4.2a Beta 5 for Windows over night. Starting indexing for L4.2a Beta 5 Mac this morning about 3 hours ago. With 5,656 Resources the processes is painful, having some indication of the progress of indexing exercise as Dave suggested will be appreciated.
JK
MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1
I use WinTail to see what is being recorded to the log, so I can see this but yes, tooltip would benefit from more info as DH suggests
Mine was stuck at 1 minute before I went to bed, probably at least a half hour. It was finished by the time I got up.
Dave Hooton:If Logos will not remove the timing estimates then they should also state what is happening:-
Mine was stuck at 11 hours for several hours, I kept tabs that something was happening by checking the indexer log: MacIndexerProgress | 846 of 866 resources indexed; total progress is 84.9%
IMHO, if they can put this type of information in the log, why can't they display it. Indexed resources and/or total progress percentage are much more informative than the bogus time estimate.
Terry Poperszky: IMHO, if they can put this type of information in the log, why can't they display it. Indexed resources and/or total progress percentage are much more informative than the bogus time estimate.
I wouldn't want to see as much detail as is in the log, but rather something like "indexed 320 resources out of 5000" where the lower number counts up (by 10's or spurts or whatever would be fine).
Either that or the percentage, doesn't really matter to me. But my point was that there is concrete information in the log, why publish the bogus time estimates rather than the more meaningful information they have available.
On the other hand, it frankly isn't that big of a deal. More a matter of curiosity on my part as to why the choice.
Rosie Perera:something like "indexed 320 resources out of 5000"
I'm fairly sure that this is exactly what we had in the first betas for Logos4 before they changed to the whole time guesstimate. I've requested a return to that from then 'til now.
Rosie Perera:Logos indexer was reporting "one minute remaining" for five hours!
It just didn't tell which minute it was waiting for
Orthodox Bishop Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."
MJ. Smith: Rosie Perera:Logos indexer was reporting "one minute remaining" for five hours! It just didn't tell which minute it was waiting for
Well, a thousand hours in God's sight are like a minute gone. So maybe it's accurate after all.
Terry Poperszky: Indexed resources and/or total progress percentage are much more informative than the bogus time estimate.
I agree. When the latest fix was released I was interested to see what the new indexing in the latest beta would do. Initially it showed I had 14+ hours to go, then it went to about 2 hours. I had to go somewhere and just before I left I checked and it showed a little over an hour left. When I returned indexing was complete and reviewing the logs it really took a little less than a half hour from start to finish. This was not a rebuild, rather the automatic merge that occurs in the new beta. My poiint is that the time estimates have never been correct and are often not even close.
Logging Tool