BUG: 14 Minute start-up

Last night while at work I tagged all of my perseus Greek language texts using my netbook. I have been going through a process of tagging and hiding resources written in languages I cannot read.

This morning I started logos on my laptop at home. It took 14 minutes of looking at the screen (that appeared in this beta cycle with the spinning pizza) that says "Syncronizing. Downloading you documents and settings."

Looking at the log it appears the majority of time was spent updating resource content, attempting to create a new index, and then canceling the process. The program did this for each of the files I tagged.

Is all of that really needed? Maybe I am not reading the log correctly, or maybe I do not understand what is happening "under the hood"; but it seems like it is trying to do too much behind the scenes at the expense of performance.

160703.Logos4.log

Find more posts tagged with

Comments

Mark Barnes

Looking at the log it appears the majority of time was spent updating resource content, attempting to create a new index, and then canceling the process. The program did this for each of the files I tagged.

That is how it works. It syncs one at at time. When that one as finished, it starts the catalog rebuild, and checks if there's another sync item. When it finds there is another one it cancels the rebuild (because it knows it's going to have to rebuild it again), and continues.

Two suggestions for logos re: this 'bug':

Add a message to the Synchronising Resources splash which says "if you click close, then the sychronising will continue in the background, but it may slow down your use of Logos" (note to Fred: you can close the box now and this will happen- but that's not self-evident).
Delay the catalogue rebuild until syncing has finished. It's pointless starting and cancelling it.

Fred Chapman

https://community.logos.com/discussion/comment/320214#Comment_320214

Delay the catalogue rebuild until syncing has finished. It's pointless starting and cancelling it.

Thanks Mark. This suggestion makes a lot of sense to me.

Many years ago when I worked construction we would frame the structure, then ruff in wiring and plumbing, then insolate, then sheetrock, then finish.

This sync and catalog process seems like the program is trying to build one wall at a time, finish it and then move to the next one. I would have hated to try and build a house like that.

tom

https://community.logos.com/discussion/comment/320229#Comment_320229

This sync and catalog process seems like the program is trying to build one wall at a time, finish it and then move to the next one. I would have hated to try and build a house like that.

[Y]

There are some bugs with the new sync that has caused long startup times. It takes my laptop over 20 minutes to start L4 now. Logos has stated that this is a known bug, and they are working on it.

From another thread:

Synchronization is actively being examined by our Development department.

DMB

https://community.logos.com/discussion/comment/320242#Comment_320242

Looking more and more like the newly announced Peshitta interlinear will role out before 4.5. Now for the latin interlinear too!

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/320214#Comment_320214

Looking at the log it appears the majority of time was spent updating resource content, attempting to create a new index, and then canceling the process. The program did this for each of the files I tagged.

That is how it works. It syncs one at at time. When that one as finished, it starts the catalog rebuild, and checks if there's another sync item. When it finds there is another one it cancels the rebuild (because it knows it's going to have to rebuild it again), and continues.

The syncing and library catalog reindexing happen in parallel. (Note that each log line has different thread IDs--the number following the timestamp.)

It's possible (on a single core system) that cancelling and restarting the library catalog index could slow down sync, but it's most likely that all the time is being spent in network I/O.

Two suggestions for logos re: this 'bug':

Add a message to the Synchronising Resources splash which says "if you click close, then the sychronising will continue in the background, but it may slow down your use of Logos" (note to Fred: you can close the box now and this will happen- but that's not self-evident).

Delay the catalogue rebuild until syncing has finished. It's pointless starting and cancelling it.

We have already implemented suggestion #1 for the next 4.5 beta.