Speed Issue

I have a i-7 3.3 GHZ processor with 8GB of Ram and am wondering if anyone can explain to me why it takes 30-35 seconds for the program to open (I am loading to a blank screen) and when I open my work space, and when I click on one of the tabs in my work space that there is a hestitation of a couple of seconds before the tab opens. Now, just the initial time after I click on the tab the first time it shows instantly the rest of the time. Just curious on the speed of opening and hesitation of showing the information when I click on the tab.

Thanks.

Find more posts tagged with

Comments

Graham Criddle

Is this on Windows or Mac?

Pastor Michael Huffman

https://community.logos.com/discussion/comment/591402#Comment_591402

Is this on Windows or Mac?

WINDOWS 8

David Taylor, Jr.

I have a i-7 3.3 GHZ processor with 8GB of Ram and am wondering if anyone can explain to me why it takes 30-35 seconds for the program to open (I am loading to a blank screen) and when I open my work space, and when I click on one of the tabs in my work space that there is a hestitation of a couple of seconds before the tab opens. Now, just the initial time after I click on the tab the first time it shows instantly the rest of the time. Just curious on the speed of opening and hesitation of showing the information when I click on the tab.

Thanks.

I find this to be the case in Windows 7 as well.

James Chandler

I have a 24G memory laptop and it takes nearly as much time to open as well. It may have to do with some indexing issue.

Rich DeRuiter

I have a i-7 3.3 GHZ processor with 8GB of Ram and am wondering if anyone can explain to me why it takes 30-35 seconds for the program to open (I am loading to a blank screen) and when I open my work space, and when I click on one of the tabs in my work space that there is a hestitation of a couple of seconds before the tab opens. Now, just the initial time after I click on the tab the first time it shows instantly the rest of the time. Just curious on the speed of opening and hesitation of showing the information when I click on the tab.

Thanks.

A large number of factors come into play here. It generally takes my system over 90 seconds to start up Logos and let it be usable. This is because of my slow hard drive and the large number of tabs I have open, and probably some other factors I'm not aware of (background tasks in Windows, anti-virus, etc.).

Dave Hooton

I have a i-7 3.3 GHZ processor with 8GB of Ram and am wondering if anyone can explain to me why it takes 30-35 seconds...

I've noticed that most super-computers tend to take longer to open and have more latency than an i5 2.53 GHz with 4 GB RAM[:D]. Seriously, it is down to the quality of the motherboard and RAM, together with their timings and the mix of other components, including the hard drive. Any computer will have better load/response times after the initial attempt because information has been stored in RAM. An SSD is the most effective way to improve the initial speed.

Mike Childs

A very interesting thread.

I use the Surface Pro 2 which has the i5 processor, 8 gig ram, and 256 SSD (plus 64 gig micro SD card). I started Logos 5 (with 5,649 resources) from Windows 8 desktop with nothing else open. The first start was 23.3 seconds before usable. Closed it. Second start it did that "preparing you library, this may take a while" thing, and it was 36.7 seconds before usable. Closed it. The third time it was 17.4 seconds before it was usable.

By usable I mean I could scroll the text, search, etc., without noticeable hesitation. One thing I did not realize while running this test, I was opening my previous workspace, and one commentary was opening in a separate floating window each time. I am not sure that had any impact on the speed, but it certainly would not have helped it.

I suppose it may be that the bigger super machine has more stuff to get started, but then more power after it starts. Pure speculation. One thing I do feel strongly about is David's statement that the best way to improve speed is an SSD hard drive. I agree. However, I had an SSD in my previous laptop along with an i7 processor, and it was still slower running Logos 5 than my Surface Pro 2.

Rich DeRuiter

https://community.logos.com/discussion/comment/591724#Comment_591724

One final thing that really, really hurts load up time is having an active search or guide window open, as the results will be populated before the system will be released for use. Closing any search windows or guides, or putting them behind another tab helps immensely with this issue.

Paul Golder

Speed reduction occurs due to de-emphasizing software efficiency in favor of other concerns like developer productivity, or possibly through the introduction of new layers of abstraction like a virtual machine or other scripting engine for the purposes of convenience when developer constraints are reduced. The perception of improved developer productivity, in the case of practicing development within virtual machine environments, comes from the developers no longer taking resource constraints and usage into consideration during design and development; this allows the product to be completed faster but it results in increases to the end user's hardware requirements to compensate, assuming that satisfactory compensation is even possible.

Dave Hooton

https://community.logos.com/discussion/comment/591724#Comment_591724

However, I had an SSD in my previous laptop along with an i7 processor, and it was still slower running Logos 5 than my Surface Pro 2.

Which makes my point about hardware architecture (design/quality/mix of motherboard and components)! But the SSD was still the best way to improve the i7 with hard drive.

Mike Childs

https://community.logos.com/discussion/comment/591808#Comment_591808

However, I had an SSD in my previous laptop along with an i7 processor, and it was still slower running Logos 5 than my Surface Pro 2.

Which makes my point about hardware architecture (design/quality/mix of motherboard and components)! But the SSD was still the best way to improve the i7 with hard drive.

[Y]