Like clicking in slow motion
I have the beta installed on my 4 1/2 year old Thinkpad T42p. I don't really have issues with search speeds or indexing speeds. But I'm really having trouble with the interface's responsiveness.
It takes more than a second for a window to close after clicking the X. When I grab the scrollbar in a resource and pull it down, it takes upward of 2 seconds for the window to catch up with my mouse. Just about anything that uses a window control takes around a second to respond to the mouse.
Other things seem fine: Typing in fields is not a problem. The resource menu (clicking on the book cover) is pretty responsive. Navigating a book with the TOC is also decent.
My Thinkpad is a Pentium M 2.0 GHz with 2GB RAM. I have not experienced this trouble running other apps, including LDLS3. Am I outside of the performance envelope?
MacBook Pro (2019), ThinkPad E540
Find more posts tagged with
Comments
Todd,
Just about everything in 4.0 is slow. Right now it could be called Four Point Slow instead of 4.0. Major, repeat, major improvements must be made in this area.
Pastor, North Park Baptist Church
Bridgeport, CT USA
Todd,
Just about everything in 4.0 is slow. Right now it could be called Four Point Slow instead of 4.0. Major, repeat, major improvements must be made in this area.
Hi Mark,
Slow performance in 4.0 isn't standard behavior. What are your system specs? Are you running it on a Mac in a virtual Windows machine? Is Indexing still running?
Melissa
Right now it could be called Four Point Slow
Mark, how old is your system? XP or Vista?
Our target for great performance is 2 years old or newer. (Though laptop/desktop/memory, etc. do make a difference, too.)
I have a machine purchased in September 2007. It is a Dell Inspiron laptop with a 2.0 GHz Core Duo processor and 2GB of RAM running Vista Business Edition with all the upgrades.
The trouble is that while I understood 4.0 to be faster it is actually slower than 3.0 in most ways. Right clicking takes a long time to bring up a menu, panes often take a long time to close (see my recent crash reports, as now they don't seem to want to close well at all), the time to generate a search report makes the whole search process slower than 3.0 (even if the search itself might be faster). Opening the Library takes a little more time in 4.0. Opening a resource from the library takes considerably longer. For example: MacArthur's commentary on Galatians takes less than a second to open in 3.0 and takes 7 seconds in 4.0 (as do most resources). The time to generate a somewhat comparable passage guide report to 3.0 is no faster, perhaps a bit slower.
I will acknowledge that I am running a seven pane layout with about 36 resources and tools open in 4.0. However I regularly use a setup in 3.0 with six pane layout and 29 resources and tools open and that setup is not as sluggish as the 4.0 setup. It is the one I am using to time against 4.0.
I am about within your target group for great performance. My opinion is that I am getting poor performance: too slow to use regularly.
Pastor, North Park Baptist Church
Bridgeport, CT USA
Bob, Melissa, and Team,
I am having similar issues, and mine have gotten worse since Beta 2. In fact, when the program is open it seems to slow my entire system down. I need to test some more and will be able to do that tomorrow.
I will include the specs too - I need to just add that to my sig. My "real" test machine is at the church. FWIW, it is a fairly new computer with good specs. I did just order more memory. I have 1gb now. I will see if that helps next week.
But as a general statement, Beta 2 is slower than Beta 1 on all 3 machines that I have it installed. Very similar to Todd's description above.
Jerry
Macbook Air (2024), Apple M2, 16gb Ram, Mac Sequoia, 1TB storage
I have also experienced the slow reaction. Scrolling is very slow. Opening Logos 4 is slow but better with beta 2. Searching has been very fast. My system is a one year old Lenovo notebook:
windows vista, intel coe 2 duo, 3 GB ram, 1.80 GHZ, 32 bit
Ver 4 does seem to respond very slowly. It often gives the (not responding) warning and then in a minute or so it gets to where it was supposed to go. Will the program become become a little more responsive as the build process continues?
Hi Todd,
We have noted these performance issues, and do plan to do some optimization in the future. As new updates come out, please let us know if you see improvements (or deterioration) in performance.
Thanks, Melissa