The Power of the Desktop, Coming to the Web

Francis
Francis Member Posts: 3,807
edited November 21 in English Forum

This is one of the descriptions of app.logos.com. This brings the question: how does it work in terms of computing power? I mean, when I run Logos locally, I need to index resources, and performance depend on the specs of the drive on which they are stored (for instance SSD being better than HDD) and of course of the other specs of my computer. 

So, I know that for now, there is not much running on app.logos.com beside accessing resources. But when it is all implemented, how will it work? What will determine how quick a complex search on app.logos.com will be? Will it be mainly dependent on the quality of the Internet connection? How will it relate to the specs of the computer from which the search is originated?

This question would be of particular interest to those who would like to use the Chromebook approach to Logos, but also for the rest of us. It would be interesting indeed to understand whether it may be advantageous to run certain stages on the desktop or in the web app.

Tagged:

Comments

  • Fred Chapman
    Fred Chapman Member Posts: 5,898 ✭✭✭

    When this was being discussed early it seemed like FL had Chromebook (and similar) users in mind. I think their goal is to create a web app that is limited only by the quality of one's internet connection. As more get's added to the web app it will be interesting to see if they can achieve and maintain performance.

    Logging Tool

  • David Mitchell
    David Mitchell Member Posts: 1,275 ✭✭✭

    While there will be certain elements that will depend on your hardware (particularly with respect to the display of certain graphics and animations), the heavy portions of guides, searches, and other data-intensive features will be running on our servers.

    David Mitchell
    Development Lead
    Faithlife

  • JT (alabama24)
    JT (alabama24) Member, MVP Posts: 36,470 ✭✭✭

    So, I know that for now, there is not much running on app.logos.com beside accessing resources.

    Not quite right. The web app already includes the passage guide and atlas.

    macOS, iOS & iPadOS | Logs |  Install

  • JT (alabama24)
    JT (alabama24) Member, MVP Posts: 36,470 ✭✭✭
    https://community.logos.com/discussion/comment/733298#Comment_733298

    By the way, here are two screen shots: L6 and Web (top 10 commentaries) for a guide on Hebrews 11:1. The list is identical. 

    macOS, iOS & iPadOS | Logs |  Install

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    What will determine how quick a complex search on app.logos.com will be? Will it be mainly dependent on the quality of the Internet connection? How will it relate to the specs of the computer from which the search is originated?

    Searching will always be done server side, so the speed of a complex search will be mostly dependent on the performance of the Logos servers.

    This question would be of particular interest to those who would like to use the Chromebook approach to Logos, but also for the rest of us. It would be interesting indeed to understand whether it may be advantageous to run certain stages on the desktop or in the web app.

    The combined speed of app.logos.com will depend on three factors:

    • Performance of Logos server
    • Speed of your internet connection
    • Performance of your browser

    I ran a Passage Guide for Romans 8:1-12 in Chrome, and profiled the performance.

    1. The Logos server took 4.91s to process the request
    2. It took only 57ms for me to download the request, which was only 18kb gzipped
    3. It took 212ms for my browser to process and display the results.

    Now, with a slower internet connection or PC, then (2) and (3) might take a little longer, but even a machine that is orders of magnitude slower than mine is still going to process the results far quicker than Logos is going to serve them.

    In other words, so long as you're running a modern browser, you don't really need to worry too much about computing power. That's Faithlife's problem, not yours.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Anthony
    Anthony Member Posts: 167
    https://community.logos.com/discussion/comment/733302#Comment_733302

    The combined speed of app.logos.com will depend on three factors:

    • Performance of Logos server
    • Speed of your internet connection
    • Performance of your browser

    I ran a Passage Guide for Romans 8:1-12 in Chrome, and profiled the performance.

    1. The Logos server took 4.91s to process the request
    2. It took only 57ms for me to download the request, which was only 18kb gzipped
    3. It took 212ms for my browser to process and display the results.

    Now, with a slower internet connection or PC, then (2) and (3) might take a little longer, but even a machine that is orders of magnitude slower than mine is still going to process the results far quicker than Logos is going to serve them.

    In other words, so long as you're running a modern browser, you don't really need to worry too much about computing power. That's Faithlife's problem, not yours.

    I just want to note that there may not be very much of a load on the servers right now. Of course I'm sure they will balance power as more users begin using it. Also, I think that's a pretty light search compared to what the full application can do. If they could take more complex searches and make them that quick...

Categories