L4 Mac very slow today

When opening L4 Mac today the Home Page took a long time to appear. Also, clicking on the Command Line does not give an instant response but take a long time before you can actually write in it. Is there somebody else experiencing this today or am I the only one!

Find more posts tagged with

Comments

crispux3

Logos 4 Mac is always slow for me. It's a system hog. I don't think they completely optimized it for the Mac. Granted, my Mac isn't as fast as what's available today, but it should still be more than capable of running this software smoothly.

I have a Macbook Pro, 2.4 Ghz intel core 2 duo, 2 GB RAM, 160 GB 7200 rpm HDD, and a 256 MB GeForce 8600M GT dedicated video card. When I run Logos 4, and go to the activity monitor, Logos 4 is always taking up the most CPU processes and uses, by far, the most memory. Everytime I run it, the fans on my system go crazy fast, like around 6,000 rpms compared to around 2,000 rpms normally. (I check it with a utility called iStat; free download from the internet).

At this point, I still prefer to use Logos 3 simply because it doesn't bog down my system when I'm using it, and I can actually multitask.

Richard Labelle

https://community.logos.com/discussion/comment/187604#Comment_187604

Thanks for your input Jeremy but usually L4 Mac for me runs pretty good. I just wanted to know if there was something happening today that would slow down L4 Mac significantly.

mab

I'm sure you aren't alone, but maybe not for the same reason. There are numerous reasons for slow performance. If you aren't indexing something newly downloaded, the easiest thing to do is to quit and try restarting Logos. Also make sure you don't have other performance-hungry apps running that you aren't in need of at the same time.

lostlogik

https://community.logos.com/discussion/comment/187606#Comment_187606

You're not the only one. It's virtually ground to a halt on my MacBook. So much so I've had to Force Quit because the menus weren't even working. I've tried fresh install and am now rebuilding the index but as I'm not the only one, guess that wasn't the issue & should've left well alone for another day. Here's hoping it's better tomorrow.