On my computer with "Internet Off" it would boot to a blank layout in a little over 10 seconds. With "Internet On" it would boot to a blank layout in about 19.5 seconds (according to the logs).

With Logos 5 booting speed is faster. With "Internet Off" I am booting to a blank layout in under 7 seconds!! With "Internet On" I am booting to a blank layout in a little over 19 seconds.

So, it seems that while the program itself boots about 3 seconds faster (30% improvement!!), the initial Internet connection takes longer in Logos 5 than in Logos 4 (Logos 5 - Internet On adds 12.5 seconds to boot; Logos 4 - Internet On adds 9.5 seconds to boot time). The end result unfortunately is that Logos 5 boots just as slowly as Logos 4.

So, here's hoping that the Logos team can find a way to optimize the Internet connection time for Logos to boot. It seems absurd that a web page with graphics can open in about .25 seconds, while Logos adds 12 seconds to just see what's new... with no graphics!

Especially since I only use Logos on 1 computer, so nothing is ever new. :)

I wonder if the Logos team could get the "Internet On" time for booting Logos when nothing has changed down from 12 seconds to .25 seconds?

So, it seems that while the program itself boots about 3 seconds faster (30% improvement!!), the initial Internet connection takes longer in Logos 5 than in Logos 4 (Logos 5 - Internet On adds 12.5 seconds to boot; Logos 4 - Internet On adds 9.5 seconds to boot time). The end result unfortunately is that Logos 5 boots just as slowly as Logos 4.

Apparently the reason it takes 16 seconds longer to boot with Internet On, is that with internet on, Logos checks for updates on start up. As I understand this, Logos must review & then report the current version status of the program and everything you own, send that to the Logos server (with how many jumps in between?), compare your version data with theirs, and then report back. While it's doing that, it's also checking the version data of all your personal document files and comparing them with what it has in its cloud and then reports back (the program doesn't know if you have more than one user - it just does the check by default). It may be taking slightly longer for you, if you added a large number of resources when you upgraded to L5.

It might be possible to rewrite this portion of the program to run last in the start-up sequence and allow us to use Logos while the program and resource version checking is going on. I don't know.

On the other hand, I look with a bit of envy at your start-up time. Mine is more than double that.

It might be possible to rewrite this portion of the program to run last in the start-up sequence and allow us to use Logos while the program and resource version checking is going on. I don't know.

I would think it should be possible. If you think about it, Logos is constantly synchronizing our layouts, open resources, checking for updates, etc. However, almost none of that is really necessary to do at boot time. The only thing that really would be "necessary" is just a quick check to see if the locally saved layout is the latest one. That is the type of check that could take .25 seconds. Then, Logos could already display everything to the user, at least as long as the user isn't displaying the "home screen".

All the other syncs don't really add anything to the Logos experience by synching at boot time. They could just as well wait until the next sync while using the program. When users start the program, they want to use it... if they need to wait until 15 seconds after using it to download the latest update to their connected Notes file from Faithlife that's simply not a problem.

That's my opinion, anyway, based on what I know about what happens at boot time. I think Logos could offer the same basic sync experience, with no drawbacks, and a boot time that would normally be 10-15 seconds faster.

Richard DeRuiter:

On the other hand, I look with a bit of envy at your start-up time. Mine is more than double that.

Actually my boot time is usually about more than what I posted here. The times posted here are for opening a blank layout, which I don't normally do. As well, in this case (as I did when I did the the posting about the boot times in Logos 4), I opened and closed the program a few times, until I started getting pretty consistent boot times, to make sure that the times I was reporting weren't just a fluke. If you repeatedly open and close Logos like that, your time will come down a little bit, the first times will always be slower.Probably parts of the program remain loaded into memory.

BTW, what most helped lower my boot times was using an SSD.

All this having been said, a big congrats to the Logos team for having improved the start up time of Logos 5 when disconnected from the Internet. And hopes that in the future the Internet connection will no longer mean waiting a long time to open Logos!

It might be possible to rewrite this portion of the program to run last in the start-up sequence and allow us to use Logos while the program and resource version checking is going on. I don't know.

This type of request was being made during the Logos 4 beta I think it would be great all of the non essential code was delayed and the desktop loaded as quickly as possible so we can get on with using the software before some of the other tasks kick off.

Last week I booted up the PC to check a couple of things before Church on Sunday and was shocked at just how long Logos 5 took to reach the point where I could use it! I know Logos is more than just a reader but this does need fixing.

It might be possible to rewrite this portion of the program to run last in the start-up sequence and allow us to use Logos while the program and resource version checking is going on. I don't know.

This type of request was being made during the Logos 4 beta I think it would be great all of the non essential code was delayed and the desktop loaded as quickly as possible so we can get on with using the software before some of the other tasks kick off.

Last week I booted up the PC to check a couple of things before Church on Sunday and was shocked at just how long Logos 5 took to reach the point where I could use it! I know Logos is more than just a reader but this does need fixing.

I don't believe the delay (at least with the internet connection on) has to do with program code. As mentioned, there is an up-front check regarding data sets. My educated guess (as one who has worked in IT) is that much of the delay is on the back-end (meaning the centralized Logos servers) as the database engine is performing its query against your data sets to determine what needs to be synced to your desktop. Considering the sheer number of Logos users, that has to be massive database in terms of raw row counts.

Having said that, modifying Logos to load "essential" components first while loading everything else in the background brings some complications. If indeed the majority of that delay has to do with back-end querying, allowing the user to immediately jump into the application prior to the background check runs the risk of integrity issues where you might update something locally (e.g. you notes) before Logos could complete its query and download the latest version of your notes. If those were notes that you created at home and then went and booted up at church and immediately opened those notes, your changes from home would not be reflected, and worse, any change you make may end up overwriting what you had previously updated.

I could be wrong about those presumptions, but based upon the performance statistics, the delay is certainly not with the actual program installed on our computers.

Here is the log from a boot of Logos 5, showing only the parts that have to do with the initial synching of Logos. It seems that basically the Logos program is "machine-gunning" the Logos web services. If I understand the log correctly, Logos sends out over 50 different web service requests to see if things are synched up correctly. So, it seems that it is not so much that the Logos servers are slow, but that you are sending and awaiting the response to over 50 different requests for info.

I would imagine that it would be possible to create a web service optimized for checking sync needs at boot time, which could consolidate all the sync info into 1 larger petition, instead of over 50 small ones. Another possibility could be to do an initial compare of just the latest changed item locally with the latest changed item on the server. I have the impression from a previous post of Bradley's that something like this has been planned, and in fact was initially planned for v4.5 (cf. http://community.logos.com/forums/p/47168/350848.aspx#350848