Ridiculously slow searching

I have Logos 4 running in a Windows 7 virtual machine in VMware Fusion and also natively on the OS X side. The following search of the entire library "History of the New Testament" takes 2.05 seconds on the Windows side and a whopping 88.2 seconds on the Mac side. I realize that this is an Alpha release, but is that normal?

Thanks,

Mark

Find more posts tagged with

Comments

Felipe Chamy

has your entire library been indexed yet. I think indexing is the way Logos has to speed up searches... I made the same search and it took me 19 seconds on Logos 4 Mac, I´m sure it could be faster but it is not 88 sec...

Terry Poperszky

I realize that this is an Alpha release, but is that normal?

Yes. Speed optimization is one of the last things that is addressed. In software development until everything works right, and all elements are present, programmers don't pay too much attention to speed.

Mark Langdon

https://community.logos.com/discussion/comment/67882#Comment_67882

Yes, that is true. I'm a developer myself. I don't have a problem with it being slow for now. It is completely indexed and running on a Early 2008 8-Core Mac Pro, so I was still a bit surprised that it is quite as slow as that. I actually just closed the program and opened it again and this time it took 11.83 sec. That's quite a bit better.

By the way, it's nice to see that this forum is so active. I'm new here but will certainly be posting more.

Mark

Russ Quinn

https://community.logos.com/discussion/comment/67894#Comment_67894

I've almost posted to this thread and another one about search speeds today.

The reason I did not post to either one is that I ran my examples twice and got inconsistent results that contradicted the point of each post.

Mark Langdon

https://community.logos.com/discussion/comment/67897#Comment_67897

Same for me. After I got the faster 11 sec. result. I did another search and it went back to taking forever.

MJ. Smith

https://community.logos.com/discussion/comment/67882#Comment_67882

This another back in the day -- for us programmers and/or analysts who had to consider performance in the early stages and have funny/sad stories of those who didn't. Of cource, it always snoed in July, we always walked uphill with the wind in our face ...

J.R. Miller

https://community.logos.com/discussion/comment/67894#Comment_67894

By the way, it's nice to see that this forum is so active. I'm new here but will certainly be posting more.

Welcome to the testing group :-)

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/67894#Comment_67894

Yes, that is true. I'm a developer myself. I don't have a problem with it being slow for now. It is completely indexed and running on a Early 2008 8-Core Mac Pro, so I was still a bit surprised that it is quite as slow as that. I actually just closed the program and opened it again and this time it took 11.83 sec. That's quite a bit better.

Since the code for searching and building the indexes is exactly the same on Windows and Mac, we suspect the differences lie in Windows using Microsoft's .NET framework which is obviously highly optimized for Windows, and Mac using the open-source Mono framework, which hasn't had the same optimization on Mac. We will get around to tweaking performance, but we're really focused on getting things implemented first. Code first, optimize later. At any rate, the optimization will likely be at the level below our application code, in the Mono runtime so we're really fixing someone else's bugs

Russ Quinn

https://community.logos.com/discussion/comment/68051#Comment_68051

Since the code for searching and building the indexes is exactly the same on Windows and Mac, we suspect the differences lie in Windows using Microsoft's .NET framework which is obviously highly optimized for Windows, and Mac using the open-source Mono framework, which hasn't had the same optimization on Mac. We will get around to tweaking performance, but we're really focused on getting things implemented first. Code first, optimize later. At any rate, the optimization will likely be at the level below our application code, in the Mono runtime so we're really fixing someone else's bugs

If that is the case, is it realistic to expect the Mac version to ever be as fast as the Windows version?

Michael Kares

https://community.logos.com/discussion/comment/68051#Comment_68051

so we're really fixing someone else's bugs

Ahhhhhhh, the nature of open-source. I'm sure the Mono folks will be really thankful....well, hopefully.

Terry Poperszky

https://community.logos.com/discussion/comment/68051#Comment_68051

We will get around to tweaking performance, but we're really focused on getting things implemented first. Code first, optimize later.

Isn't that what I said??? [:P]

Jerry Walker

https://community.logos.com/discussion/comment/68056#Comment_68056

If that is the case, is it realistic to expect the Mac version to ever be as fast as the Windows version?

I was wondering that same thing, but I really wanted it to be faster then the PC side because if you look at Logos for Mac 1.2.2 it was much much faster then the windows version. So you ask a good question hopefully we can get a response to it.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/68082#Comment_68082

Yes, but sometimes it's useful to hear it straight from the horse's mouth.

Terry Poperszky

https://community.logos.com/discussion/comment/68385#Comment_68385

Yes, but sometimes it's useful to hear it straight from the horse's mouth.

Tempting a brother in the Lord with a straight line such as this, must be a sin.