Perseus Collection & Passage Guide

Since downloading the Perseus collection, it wreaks havoc with creating a passage list especially when adding a reference to 1 Cor 13:4-13, or 1 Jn 4:11-12. It bogs down the computer so that it takes almost 5 mins for the reference to even populate the field after typing.

Is there a fix?

Find more posts tagged with

Comments

NB.Mick

Since downloading the Perseus collection, it wreaks havoc with creating a passage list especially when adding a reference to 1 Cor 13:4-13, or 1 Jn 4:11-12. It bogs down the computer so that it takes almost 5 mins for the reference to even populate the field after typing.

Is there a fix?

has indexing finished? Normally those resources shouldn't be in the way, but indexing 1000s of resources will slow down the system very much.

Ellis I. Washington

https://community.logos.com/discussion/comment/524791#Comment_524791

This happens when indexing is not happening. It's more related to books with numbers in front, which causes similar books from the Perseus collection to pop into the window even while attempting to enter the reference.

Mark Barnes

https://community.logos.com/discussion/comment/524792#Comment_524792

This happens when indexing is not happening. It's more related to books with numbers in front, which causes similar books from the Perseus collection to pop into the window even while attempting to enter the reference.

This shouldn't cause the slow down that you're describing (mine populates immediately, even with Perseus). Can you let us know more about your computer and version of Logos?

Ellis I. Washington

https://community.logos.com/discussion/comment/524825#Comment_524825

I'm running Logos 5.1a SR-1 on a iMac version 10.7.5 w 2.66 GHz Intel Core Duo and 4 GB memory.

I've encountered this on my MacBook Pro as well.

My apologies to NB.Mick, I believe it WAS indexing at first the last time this occurred but I subsequently paused indexing which didn't seem to help much.

Mark Barnes

https://community.logos.com/discussion/comment/524942#Comment_524942

My apologies to NB.Mick, I believe it WAS indexing at first the last time this occurred but I subsequently paused indexing which didn't seem to help much.

Let's wait for indexing to finish, and see what the speed is then. I don't know what impact a half-completed index would have on this issue. I'll also bow out and let the Mac experts take over. Perhaps one could confirm whether there is any slowdown for them?

fgh

https://community.logos.com/discussion/comment/524947#Comment_524947

I don't know what impact a half-completed index would have on this issue.

Depends on when exactly the pausing is done, I would think. The first part (the actual indexing) mainly uses the CPU, so pausing then ought to give a substantial performance improvement, but the second part (the merging of the new index with the existing one) uses all the RAM it can get hold of, and doesn't release it until it's done, so pausing then will still leave you with a very sluggish machine.

Indexing rule number 1: never let the indexing start unless you a) don't need the computer in the near future, or b) have plenty of free RAM, or c) have computer specs that allows you to forget about a) and b).

Lynden O. Williams

https://community.logos.com/discussion/comment/524970#Comment_524970

Thanks for the advice fgh.