BUG: Editing morph-based visual filter so slow as to be unusable

Page 1 of 1 (5 items)
This post has 4 Replies | 1 Follower

Posts 524
Stuart Robertson | Forum Activity | Posted: Thu, Dec 30 2010 4:09 AM | Locked

Trying to edit a morphology-based visual filter, based on AFAT, but the drop-downs that appear after I type @ comsume vast amounts of CPU and take 3 to 5 seconds to appear, and then each click on the dropdown, or each keystroke takes another 3-5 seconds to cause any response.  It's taken almost a minute to create a simple filter with two verbal forms (imperative, insistent imperative, etc).

Not sure where the CPU is going but it's pretty unusable as it stands.

Posts 4077
Melissa Snyder | Forum Activity | Replied: Fri, Dec 31 2010 7:30 AM | Locked

My system barely registers CPU activity when selecting from the Morph chooser in a Visual Filter document when that's the only panel open. It spikes about half way after I press spacebar when selections are complete. Where I see more CPU activity, and a slowdown, is when I'm scrolling through the AFAT, which is a known issue. Many of these optimization issues will be addressed in coming releases.

Posts 524
Stuart Robertson | Forum Activity | Replied: Fri, Dec 31 2010 11:35 AM | Locked

I'm really glad for you :-)  But, seriously though, I'm not as fortunate when it comes to Logos performance.  How do we get this investigated without me having to create another screencast to "prove" the problem?

Posts 4077
Melissa Snyder | Forum Activity | Replied: Fri, Dec 31 2010 12:37 PM | Locked

Stuart Robertson:

I'm really glad for you :-)  But, seriously though, I'm not as fortunate when it comes to Logos performance.  How do we get this investigated without me having to create another screencast to "prove" the problem?

Stuart Robertson:

I'm really glad for you :-)  But, seriously though, I'm not as fortunate when it comes to Logos performance.  How do we get this investigated without me having to create another screencast to "prove" the problem?

 

It's not necessary to 'prove' the problem. I don't doubt what you're experiencing. I only mention my experience so that it's clear it's not a general bug affecting all users. Logs are the next best way for the developers to track down the problem if we're not able to reproduce the problem here. It's also helpful for them to know what the system specs are, what software is running concurrently, and what peripherals are connected, if any.

Posts 524
Stuart Robertson | Forum Activity | Replied: Fri, Dec 31 2010 5:14 PM | Locked

Thanks Melissa.

I'm running the latest beta (Logos Bible Software 4.2a Beta 3 (4.21.4.8572)) on Snow Leopard 10.6.5, Macbook Pro 17", i7 2.66GHz, 8GB RAM, 500GB 5400rpm disk.

Other apps running are Mail, Path Finder, Chrome, Text Edit.  No peripherals connected (not even an external mouse or display).  I will capture logs tonight and upload them.

Page 1 of 1 (5 items) | RSS