Long delays in The Mishnah

http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/78/8080.Logos4.log

I'm experiencing some really long delays in the Mishnah:

Neusner, Jacob. The Mishnah : A New Translation. New Haven, CT: Yale University Press, 1988.

LLS:29.5.1
2010-01-15T18:19:58Z
MISHNAH.logos4

For instance when opening the book, the delay is several seconds of "not responding" then jumping from say: Baba Batra 5:3 --> Baba Qamma1:1 the delay is again quite long.

Logs attached.

Find more posts tagged with

Comments

Melissa Snyder

Did this start happening recently, or has it always been this slow in opening and navigating? If recently, have you added any notes, highlighting, etc., or did it start after an update?

TCBlack

https://community.logos.com/discussion/comment/125845#Comment_125845

I do not recall it being this slow at an earlier beta, but I don't use it that often.

When I first bought it, I was able to bounce around it rather quickly. But I'm up to RC1 now and I do not know when the speed issue was introduced.

Melissa Snyder

https://community.logos.com/discussion/comment/126264#Comment_126264

I do not recall it being this slow at an earlier beta, but I don't use it that often.

When I first bought it, I was able to bounce around it rather quickly. But I'm up to RC1 now and I do not know when the speed issue was introduced.

I don't have long delays, but navigation is definitely not as snappy as other resources, and it takes about 5 secs to open vs 1-3 secs for other books. We'll take a look at your log.

Mark Barnes

https://community.logos.com/discussion/comment/126295#Comment_126295

I'm not trying to compete, but my performance in opening the Mishnah is even worse:

2010-05-06 19:34:18.8562 1 Info AppCommand (24.65s) Executing command: Resource|Id=LLS:29.5.1

Interestingly, I just ran that test on a different machine to the one I normally have the problems on, so it appears my problems are related to my account (or at least my shared configuration). I won't hijack Thomas' post, but will follow up on my own.