Start to Home Page display on a fast laptop - 75 seconds!

I am now on the fastest MacBook Pro Apple sells, a 2017 version with upgraded CPU and upgraded PCIe 2 TB SSD, 16 GB of 2133MHz RAM. Verbum 7.8 RC 1 is very slow to start up, it takes 75+ seconds from the first frame appearing to the home page coming up. Nothing can be done until this completes.
I have deleted all my visual filters, I can't use the feature anymore it makes the system too slow. I deleted a number of my Collections that had large populations. I deleted tags that also were used on a large number of resources. I don't use many Layouts any more due to performance problems, just some basic ones - I am happy to delete any/all of those if that will get this to run acceptably. I have 25,000+ resources, that and the associated overhead of all the features for a library this size have been a continuing problem, I made a mistake buying so many resources over the years. Given my situation, I am happy to delete some other stuff to make this run well, if that will help.
I have attached the log file - is it possible someone sees something obvious I can delete that this can start up in a reasonable time on a very fast Mac laptop? I have looked through the log, I surely may have missed something but it seems like it just does too much and all the little pieces make it take a very long time. I hope something can be done.
Again, this is VERBUM - MAC.
Thanks if anyone has any ideas, I would be greatly appreciative of any assistance!
Comments
-
Don Awalt said:
if anyone has any ideas
Personally, I have no use for the home page. Have you tried changing the settings to open to a blank (or basic) layout?
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Looking at the log, it seems that the app is spending most of its time building collections. You still have a lot of collections and many of them have a lot of terms to match. Some of your individual collections take 4-5 seconds to finish building. I too have a lot of collections but I don't experience that problem, presumably because my library is is about 1/5 the size of yours. With the newest beta, my 3-yr old MacBook Plus starts Logos in less than 20 seconds.
I suppose you could hide a significant portion of your library or remove the collections that have large rules (or both).
MacBook Pro (2019), ThinkPad E540
0 -
Thanks for the report, Don. We'll take a look.
0 -
Just ruminating Don...
I don't think that the size of your library per se is the cause of the slowness.
Actually Todd is probably right about the Collections (or more accurately the collection rules) being a major contributor.
It seems to me that the program is doing things before opening that might well be left until later. If the collections were built after opening you might still have to wait 75 seconds (or more) after opening the programme to get to use that last compiled collection but that would be a worst case scenario pretty much everything else would be a bonus.
tootle pip
Mike
Now tagging post-apocalyptic fiction as current affairs. Latest Logos, MacOS, iOS and iPadOS
0 -
Thanks for the analysis guys!
If the analysis points to Collections, then I would suggest this sounds like something added to the program to make Collections slower. My reason for saying this, I checked on the documents web page for my account, my last addition/update of a Collection was Sept. 27 2016. I looked at the collections that changed in 2016, and they were not additions, just minor tweaks. Also, I just tried this on a Windows 10 laptop with lower specs than the Mac, a circa 2014 HP laptop, and from first frame to Home Page it took only 5 seconds!!
So to me this sounds like some problem with the Mac Verbum. In lieu of removing all my Collections, maybe I should wait to hear if Phil/FL identify anything?
0 -
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Performance hits due to a larger library shouldn't outweigh the benefits of that larger library.
Considering that we're encouraged to upgrade our libraries every time a new version comes out (which contributes to FL's revenue stream), any step that FL can take to improve performance would alleviate (startup) consequences for all of us.
Phil Gons (Faithlife) said:Thanks for the report, Don. We'll take a look.
If FL would add denomination/theology tags, many of these complex collection rules that we use could significantly be simplified, helping to improve time spent building these collections. (This has been requested on the forum, as well as on uservoice.)
While it would make a more significant (wall-clock) difference for people like Don, even shaving off a couple seconds for many of us with much smaller libraries could still bring many of us a 10% gain (e.g. going from 20 to 18 seconds at launch).
Thanks, Phil, for all that has been done, is being done, and will be done to improve performance!
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
I think the evaluation of collections in the background is a red herring. To me, the problem looks like these lines:
2017-07-17 19:39:51.2888 | ERROR | 5 | ApplicationUtility | Error handling response (GET https://notificationsapi.logos.com/v1/notifications?status=Unread&limit=3&aggregate=False). ~WebException: Error: SendFailure (Error writing headers)
2017-07-17 19:39:51.3000 | WARN | 5 | FaithlifeNotificationsHomePageTileProvider | Error fetching notifications: Error handling response. Request: GET https://notificationsapi.logos.com/v1/notifications?status=Unread&limit=3&aggregate=False, GET - https://notificationsapi.logos.com/v1/notifications?status=Unread&limit=3&aggregate=False ()
2017-07-17 19:39:51.3000 | INFO | 5 | HomePageTileProvider | (1m 14.5s) Generating faithlifeNotifications tilesIt looks like it took 75s to try to request Faithlife notifications tiles (which would block the display of the home page) until the request finally failed. (It looks like updating licenses also failed, but some other web services may have worked.) I think it's a coincidence that this happens after all the collection rules have been evaluated, but I guess I don't know for sure.
I'll let the team perform the full analysis (since it sounds like Phil will be notifying them) but can you provide any information about your Internet connection, firewall software, AV scanner, etc. that might be helpful for them understanding why some web service requests might be failing?
0 -
but can you provide any information about your Internet connection, firewall software, AV scanner, etc. that might be helpful for them understanding why some web service requests might be failing?
Interesting question that Bradley
Care to share which 'firewall software', 'AV Scanner', etc Faithlife install on their Macs?
I have never bothered with anything that wasn't built into MacOS!
tootle pip
Mike
Now tagging post-apocalyptic fiction as current affairs. Latest Logos, MacOS, iOS and iPadOS
0 -
Thanks for looking at the log Bradley!
My internet is very fast - 180 Mbps down, 24 Mbps up. I just checked the cable modem, only one warning error reported by the modem in the last 2 weeks. So I think the network connection is solid. I also just did a speed test and it's getting correct speeds.
I have a Motorola SB8200 (DOCSIS 3.1) modem, and am using the Google WiFi throughout the house. I doubt this or the network is the issue, as the aforementioned Windows laptop that came up in 5 seconds is on the next table, using all the same network infrastructure.
On the Mac, like Mike I do not have anything other than macOS Sierra installed - no AV, no beta software of any type OS or apps. Is there anything I can test, program to run, stats to measure etc.? I have looked at the activity monitor, even with Verbum running I am using about 12GB of memory and the laptop has 16GB. Gobs of disk space available.
0 -
PS - I found the firewall under System Preferences/Security & Privacy, as a test I just turned it off entirely, fired up Verbum, and it took 84 seconds. So it's probably not that.
0 -
Don Awalt said:
I am now on the fastest MacBook Pro Apple sells, a 2017 version with upgraded CPU and upgraded PCIe 2 TB SSD, 16 GB of 2133MHz RAM. Verbum 7.8 RC 1 is very slow to start up, it takes 75+ seconds from the first frame appearing to the home page coming up. Nothing can be done until this completes.
I have deleted all my visual filters, I can't use the feature anymore it makes the system too slow. I deleted a number of my Collections that had large populations. I deleted tags that also were used on a large number of resources. I don't use many Layouts any more due to performance problems, just some basic ones - I am happy to delete any/all of those if that will get this to run acceptably. I have 25,000+ resources, that and the associated overhead of all the features for a library this size have been a continuing problem, I made a mistake buying so many resources over the years. Given my situation, I am happy to delete some other stuff to make this run well, if that will help.
I have attached the log file - is it possible someone sees something obvious I can delete that this can start up in a reasonable time on a very fast Mac laptop? I have looked through the log, I surely may have missed something but it seems like it just does too much and all the little pieces make it take a very long time. I hope something can be done.
Again, this is VERBUM - MAC.
Thanks if anyone has any ideas, I would be greatly appreciative of any assistance!
Don,
Can you please retest this in 7.8 RC 2 (7.8.0.0025). We believe some changes that were made fixed this issue. If it is still a problem your new logs will provide additional information that will help diagnose things further.
0 -
HI Philana, I did the update of the software it was 7.8.0.0026, is that what you meant, you said .0025?
After the update, I exited, deleted the log file so it would be fresh, and tried again. It was actually around 83 seconds, so it does not appear to have made a difference. Log file attached...
0 -
Don Awalt said:
HI Philana, I did the update of the software it was 7.8.0.0026, is that what you meant, you said .0025?
After the update, I exited, deleted the log file so it would be fresh, and tried again. It was actually around 83 seconds, so it does not appear to have made a difference. Log file attached...
Hi Don,
That is correct, sorry about the wrong build number, I inadvertently copied the wrong build number. I'll have the team take a look.
0