4.0b Beta 3: (Performance) Very slow boot: 45 seconds on a fast machine

Rosie Perera
Rosie Perera Member Posts: 26,194 ✭✭✭✭✭

Just trying to nail down some areas that need performance tuning.

After a cold boot on my machine, with nothing else running and no indexing going on, Logos takes 45 seconds to boot up into a simple layout with just ESV open.

Desktop | Windows Experience Index 5.6 | Intel Core2 Quad CPU Q6600 (2.40 GHz) | 8 GB RAM | NVIDIA GeForce 9800 GT w/ 512 MB RAM | Windows Vista Ultimate 64-bit SP2.

Log file attached: 4540.SlowBoot.zip

EDIT: Note that ESV was open already last time I closed Logos, so it's opening it up by itself, I'm not interacting with it at all. And the Interlinear panel was open. I'll test it again with this stuff closed. But still, 45 seconds to open up with one resource you had open last time is pretty slow!

Comments

  • Terry Poperszky
    Terry Poperszky Member Posts: 1,576 ✭✭✭

    After a cold boot on my machine, with nothing else running and no indexing going on, Logos takes 45 seconds to boot up into a simple layout with just ESV open.

     

    Well, on my machine it is a couple of seconds slower than B2, but not as slow as you are seeing:

    Cold boot, initial start: 21 seconds

    2nd start: 15 seconds

    MBP 2.8 Mhz, 4Gb Ram, Fusion 3.01, Win 7

     

     

  • Kevin A. Purcell
    Kevin A. Purcell Member Posts: 3,421 ✭✭✭

    I just installed beta 3 after I had already done the speed test on beta 2.

    Beta 2 = 22 seconds

    Beta 3 = 14.8 seconds.

    Dr. Kevin Purcell, Director of Missions
    Brushy Mountain Baptist Association

    www.kevinpurcell.org

  • Lynden O. Williams
    Lynden O. Williams MVP Posts: 9,020

    Cold booth took an unbelievable 55 seconds, including opening up the Esv.

    Windows 7 Home Premium. The beta is installed on a limited user which seems to run faster, as it has less stuff loading up at startup.

    image

    Mission: To serve God as He desires.

  • Lynden O. Williams
    Lynden O. Williams MVP Posts: 9,020

    After closing Logos and restarting it to a blank desktop, it took 15 seconds.

    Mission: To serve God as He desires.

  • Greg Gray
    Greg Gray Member Posts: 136 ✭✭

    My start up time is near double what it was for 4a (plus a wait time for parallel resources to load).

    4a was 22 seconds.

    4b is 22 seconds until I can see my layout, but then another 18 seconds until the little spinning wheel goes away and the program will respond to any commands.

     

    Also, on my system it is almost another 25 seconds before all of my parallel resource icons are visible.

     

    So 4a was 22 seconds to be able to use the program (and all of its features)

    4b is 22 seconds to load, 18 seconds to "think", 25 seconds to load parallel resources tool - for a total of 65 seconds.

     

  • Melissa Snyder
    Melissa Snyder Member Posts: 4,702 ✭✭✭

    Has performance improved in Beta 9? 

  • Rosie Perera
    Rosie Perera Member Posts: 26,194 ✭✭✭✭✭

    Has performance improved in Beta 9? 

    Yes, it is faster. It boots up to a layout with just ESV open with interlinear panel in about 18-20 seconds now.

    But....there's still a lot of that unnecessary and visually sloppy repainting going on -- windows getting created visible the wrong size and then repainting at their full maximized size (I run Logos maximized all the time and it remembers that when it opens back up again).  If development could pay attention to my suggestion to create those windows invisible first and then set them to visible only after all their content has been painted, then even more performance improvements will be achieved, and the sloppy boot sequence would be cleaned up. And why can't they be created the correct size from the get-go? Why create them the default size and then resize them after?

    You said you'd reported my previous thread about this (http://community.logos.com/forums/t/7608.aspx) to development, but it sounds like they haven't taken it into account yet. Are they open to being nudged about it, do you think?

  • MJ. Smith
    MJ. Smith MVP Posts: 55,544

    .there's still a lot of that unnecessary and visually sloppy repainting going on -- windows getting created visible the wrong size and then repainting at their full maximized size

    Very true

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Under a warm booth, a blank desktop is taking twelve seconds.

    Mission: To serve God as He desires.


  • Under a warm booth, a blank desktop is taking twelve seconds.


    That should have said restarting Logos takes twelve seconds.

    Mission: To serve God as He desires.

  • George Allakhverdyan
    George Allakhverdyan Member Posts: 1,075 ✭✭✭

    Has performance improved in Beta 9? 

    And why can't they be created the correct size from the get-go? Why create them the default size and then resize them after?

    You said you'd reported my previous thread about this (http://community.logos.com/forums/t/7608.aspx) to development, but it sounds like they haven't taken it into account yet. Are they open to being nudged about it, do you think?

    Rosie I have repro'd the exact behavior with My Library window docked in a panel but on my computer it is almost unnoticeable it happens so quick. I looked up that case and it does have a link to your post and it has a link to this thread now too.

  • Rosie Perera
    Rosie Perera Member Posts: 26,194 ✭✭✭✭✭


    Has performance improved in Beta 9? 

    And why can't they be created the correct size from the get-go? Why create them the default size and then resize them after?

    You said you'd reported my previous thread about this (http://community.logos.com/forums/t/7608.aspx) to development, but it sounds like they haven't taken it into account yet. Are they open to being nudged about it, do you think?

    Rosie I have repro'd the exact behavior with My Library window docked in a panel but on my computer it is almost unnoticeable it happens so quick. I looked up that case and it does have a link to your post and it has a link to this thread now too.


    Thanks, George.  You must have a very fast computer indeed if it's barely noticeable. My Windows Experience Index is 5.6. My system specs include:
    Processor: Intel Core 2 Quad Q6600 @ 2400 MHz.
    Physical Memory : 8192 MB (4 x 2048 DDR2-SDRAM )
    Video Card : NVIDIA GeForce 9800 GT

    And I'm still seeing a noticeable flashing of all these windows of different sizes, which takes about 10 seconds from the time the Logos app window is first visible to the time all the flashing stops, even with this simplest layout of just ESV open on startup.


  • Has performance improved in Beta 9? 

    And why can't they be created the correct size from the get-go? Why create them the default size and then resize them after?

    You said you'd reported my previous thread about this (http://community.logos.com/forums/t/7608.aspx) to development, but it sounds like they haven't taken it into account yet. Are they open to being nudged about it, do you think?

    Rosie I have repro'd the exact behavior with My Library window docked in a panel but on my computer it is almost unnoticeable it happens so quick. I looked up that case and it does have a link to your post and it has a link to this thread now too.


    George I have to concur with you, but I have experienced what Rosie is saying this evening/morning, even with Beta10.

    Mission: To serve God as He desires.


  • Under a warm booth, a blank desktop is taking twelve seconds.

    That should have said restarting Logos takes twelve seconds.

     


    Did a cold boot and L4 took 48 seconds to load and display the Net Bible. Closed software and restarted, this time it took 13 seconds to load the same screen.

    Windows 7 Home Premium, 64 Bit, 4GB RAM, Intel Core 2 Duo @2.2 GHZ.

    Mission: To serve God as He desires.

  • George Allakhverdyan
    George Allakhverdyan Member Posts: 1,075 ✭✭✭


    Thanks, George.  You must have a very fast computer indeed if it's barely noticeable. My Windows Experience Index is 5.6. My system specs include:
    Processor: Intel Core 2 Quad Q6600 @ 2400 MHz.
    Physical Memory : 8192 MB (4 x 2048 DDR2-SDRAM )
    Video Card : NVIDIA GeForce 9800 GT

    And I'm still seeing a noticeable flashing of all these windows of different sizes, which takes about 10 seconds from the time the Logos app window is first visible to the time all the flashing stops, even with this simplest layout of just ESV open on startup.


    I like your computer specs! Although I am running:

    Processor: Intel Core 2 Quad Q9550 @ 3200MHZ

    Memory: 4 GB (2 x 2048 @ 973MHz ~ PC8500 DDR2)

    GPU: Nvidia 8800GT

    I don't remember my windows exp rating I will update that when I'm at home. I'm wondering how it does that on your computer even with a simple layout, does it do it with a blank layout?

  • Rosie Perera
    Rosie Perera Member Posts: 26,194 ✭✭✭✭✭


    I'm wondering how it does that on your computer even with a simple layout, does it do it with a blank layout?


    Yes, it does it with a blank layout too. Here's a video of it, slowed down to half speed so you (and the developers) can better see all the unnecessary window moving and resizing.

    [View:http://content.screencast.com/users/rosiep/folders/Default/media/c0f43d1a-9367-4dd8-98e8-f314780f35a5/Boot1_controller.swf:640:498]

    I can see 5 distinct window operations going on, when the users should be seeing just one at this point:

    1) Main window is created (visible) default size in default position on screen.
    2) Main window is maximized.
    3) Main window is restored to default size in default position.
    4) Main window is moved (still same size) to upper left corner of screen
    5) Main window is maximized.

    All of that should not be happening. The main window should be created maximized to begin with, since the last time I closed Logos I left it maximized. The Windows API has an option for creating a window already maximized. You don't need to create it and then reposition and then resize it after creating it.

    Here it is in real time. All the flashing is still quite noticeable:

    http://www.screencast.com/t/YTU2OTVmNWI

This discussion has been closed.