Why does it take so long for Logos Mac to index?

I downloaded and installed Logos 4 for Windows on VMware and it took about five hours to index. Now, I've downloaded and am indexing Logos 4 for Mac. It reports that it needs another 34:31 to index. I know Logos for Mac is not ready for prime time, but this doesn't make sense to me. If anything, it should index faster in a native format as opposed to a virtual machine. Anyone have any clue why? If not, I thought I would report it here anyhow, so that the Logos techies would know how long it is taking as I think it is generally not practical to have to take two days to index your files. Hopefully a future release will address this!

Find more posts tagged with

Comments

Scott West

I posted a thread on this http://community.logos.com/forums/t/4147.aspx several days ago.

It seems to be a real issue. Since the latest build of A2 my version quits immediately. The indexer runs constantly even using Caffeine and the indexer.log remains at 0 bytes.

BTW, I use Parallels v5 and Win 7. The indexer took about 5 or so hours but it finished and Logos 4 works great in that world.

Titus 3:5ff

Donovan R. Palmer

https://community.logos.com/discussion/comment/33905#Comment_33905

I posted a thread on this http://community.logos.com/forums/t/4147.aspx several days ago.

It seems to be a real issue. Since the latest build of A2 my version quits immediately. The indexer runs constantly even using Caffeine and the indexer.log remains at 0 bytes.

BTW, I use Parallels v5 and Win 7. The indexer took about 5 or so hours but it finished and Logos 4 works great in that world.

I'm going to let it index all of today. If it is still hoovering around 34 hours, then I'll pull the plug on it and forget about trying to contribute to the beta efforts on this version. It just isn't practical to tie my computer up for three days just to index some files!

Scott West

https://community.logos.com/discussion/comment/33907#Comment_33907

You don't have to wait that long.

You can check the indexer.log file and see if it's doing anything.

The path is Users>your folder>Library>Application Support>Logos 4>Indexer.log

You can double click the file and it will open in console. Currently mine looks like this.

Note that it is failing at line 1441 of the process. Same line it was failing at the last A2 build. Because of this it's pointless to keep indexing. Since the process runs if the computer is active I let it keep running and failing. It will keep failing until they fix. But I don;t let that stop me from using the machine.

Titus 3:5-7

Donovan R. Palmer

https://community.logos.com/discussion/comment/34216#Comment_34216

You don't have to wait that long.

You can check the indexer.log file and see if it's doing anything.

The path is Users>your folder>Library>Application Support>Logos 4>Indexer.log

I'm getting the same errors that you list above. It has gone down from saying it has 34 hours when I got up this morning to now about 8. I don't know if I should believe it or not.

Anyhow, as I am brand new to L4 for Mac, can anyone tell me how long Alpha 2 has been out and roughly how frequently updates are coming? I hope this is in the next fix. I assume Team Logos reads these forums do they?!?

J.R. Miller

https://community.logos.com/discussion/comment/34230#Comment_34230

Anyhow, as I am brand new to L4 for Mac, can anyone tell me how long Alpha 2 has been out and roughly how frequently updates are coming? I hope this is in the next fix. I assume Team Logos reads these forums do they?!?

It was released for us on Nov 2nd.

Bob says we can expect updates every couple weeks.

The new way Logos set-up the discliamer page is making it hard to link to directly, so here it is on my blog

http://www.morethancake.org/2009/11/bible-study-reimagined-for-your-mac.html

Wes Saad

https://community.logos.com/discussion/comment/33907#Comment_33907

I'm going to let it index all of today. If it is still hoovering around 34 hours, then I'll pull the plug on it and forget about trying to contribute to the beta efforts on this version. It just isn't practical to tie my computer up for three days just to index some files!

Donovan,

I wouldn't give up on the beta completely, but maybe let them roll out a few versions before jumping back in. I imagine indexing issues are getting a lot of attention so I am hopeful that we will soon see real improvement in this area.

I'm having some of the same problems as you. For me, on one machine indexing finished overnight. On another, I can't get it to finish, it currently says something like 35+ hours.

Jason Hauser

https://community.logos.com/discussion/comment/34216#Comment_34216

I am getting the same indexing error for line 1441 mentioned above. The time remaining seems to just be standing still and occassionally bumping up a little higher. Does this mean I have to start all over? How do I prevent this from happening again?

Ken

https://community.logos.com/discussion/comment/34254#Comment_34254

I would have to agree with Donovan. I do not have the time to index for days, the download alone for my library took 9 hours. I did that first on the Mac beta, which probably was not wise because the product is so far from being finished....and then I did it again through Virtualbox in Windows...so...I upgraded my library on Sunday, but I have yet to see Logos 4 run because of two days of downloads, 3 days of index, and still more indexing on the Windows side.

Does anyone know a time frame for the final Mac release? To be honest, I am still waiting for the Mac release on the version 3 product, but my understanding is that is a dead project at this point....just never got close to the capability on the Windows side.

I will continue to walk with patience, I love the video of Logos 4, can't wait to see it up and running on either my Windows virtual system or my Mac.

Donovan R. Palmer

https://community.logos.com/discussion/comment/35814#Comment_35814

Does anyone know a time frame for the final Mac release? To be honest, I am still waiting for the Mac release on the version 3 product, but my understanding is that is a dead project at this point....just never got close to the capability on the Windows side.

It is a dead project, but Logos has said that they plan to release a way for you to read any new resources that you may have purchased in your upgrade to L4 with the old 1.2.2 engine.

I am under the impression that the install goes a lot faster if you have the DVD and don't have to download all the files. That doesn't help you now. And it's worse for Mac users who use Windows as well, because the resources aren't shared, so we have to download them twice!

Ken

https://community.logos.com/discussion/comment/35895#Comment_35895

THanks for the reply.

Any ideas then on how quickly this Alpha/Beta process will be before we see a functional Logos 4 for Mac?

I just download Alpha 3, indexing again (sigh), but the app still does not seem to have much functionality for Bible study.

Donovan R. Palmer

https://community.logos.com/discussion/comment/36733#Comment_36733

Any ideas then on how quickly this Alpha/Beta process will be before we see a functional Logos 4 for Mac?

I just download Alpha 3, indexing again (sigh), but the app still does not seem to have much functionality for Bible study.

Pragmatically, I'm not expecting to fully use and abuse it for at least six months. That's my opinion and should not be taken as anything other than a guess. Fortunately, L4 Windows is running very well under Fusion for me.

David Sholar

https://community.logos.com/discussion/comment/36816#Comment_36816

Hi Donovan - I too am running L4 on Fusion 3.0. But it does run pretty slow for me. Would you let me know what Fusion settings work best for you? Mine is currently sent for 1Gig of Ram. (using Macbook Pro with total of 4g). Thanks much.

Donovan R. Palmer

https://community.logos.com/discussion/comment/36823#Comment_36823

Hi Donovan - I too am running L4 on Fusion 3.0. But it does run pretty slow for me. Would you let me know what Fusion settings work best for you? Mine is currently sent for 1Gig of Ram. (using Macbook Pro with total of 4g). Thanks much.

There are people on these forums that know more than I do about Fusion, but from what I have gathered from them, you need 2GB of RAM. My settings are:

Bare bones XP installed on a new Fusion 3.0 machine. There are speed improvements that you only get by creating a new machine on Fusion 3.0, as opposed to using a machine created on Fusion 2.x.
Under your fusion settings for the XP machine, you need 2 GB of Ram and plenty of drive space allocated. I have 80GB allocated. Jack has allocated more. Some suggest using the pre-allocating space option, but I haven't seen any difference. You can try both.
Under settings of your fusion machine, turn off graphics acceleration.
On XP, on advanced settings for your video, turn graphics acceleration down to minimum (one step above off)
You can, if you wish, once Logos is running to run Task Manager and assign "High Prioriety" to the application. I haven't seen any improvement in my case because I am not really running anything else on XP other than antivirus, so this is probably why it makes no difference.

HTH.

Donovan

Jack Caviness

https://community.logos.com/discussion/comment/36833#Comment_36833

There are people on these forums that know more than I do about Fusion, but from what I have gathered from them, you need 2GB of RAM. My settings are:

Bare bones XP installed on a new Fusion 3.0 machine. There are speed improvements that you only get by creating a new machine on Fusion 3.0, as opposed to using a machine created on Fusion 2.x.

Under your fusion settings for the XP machine, you need 2 GB of Ram and plenty of drive space allocated. I have 80GB allocated. Jack has allocated more. Some suggest using the pre-allocating space option, but I haven't seen any difference. You can try both.

Under settings of your fusion machine, turn off graphics acceleration.

On XP, on advanced settings for your video, turn graphics acceleration down to minimum (one step above off)

You can, if you wish, once Logos is running to run Task Manager and assign "High Prioriety" to the application. I haven't seen any improvement in my case because I am not really running anything else on XP other than antivirus, so this is probably why it makes no difference.

I can't add much to the excellent summary Donovan provided, but I will add a few remarks. I am still using Fusion 2, and the performance is acceptable. I would not pre-allocate disk space; it does not increase the speed, and it needlessly ties up disk space. I did not find that assigning "High Priority" in the Windows Task Manager increased the speed of L4. Rather, I had a ghost following my cursor. Like Donovan, I am only running L4 and anti-virus software, so there is really nothing to take processor time from (bad grammar, but then, I am American, and we seem to make our own rules for the Queen's English [:D]).

Jack

Steve Hultquist

https://community.logos.com/discussion/comment/36851#Comment_36851

I downloaded A3 today and it's indexing (again). My big issue is how much of my processor it takes in doing that indexing. I would expect indexing to control the amount of CPU it uses to a reasonable amount...

Dewayne Davis

https://community.logos.com/discussion/comment/36833#Comment_36833

Under your fusion settings for the XP machine, you need 2 GB of Ram and plenty of drive space allocated

I read somewhere to allocate 1.3G of RAM. I have 4G in my Macbook and assigned 1.3G to the Fusion 2.06 VM. I have no complaints and feel it is optimal. I think it ran worse when I allocated 2G to the VM.

Donovan R. Palmer

https://community.logos.com/discussion/comment/37456#Comment_37456

I read somewhere to allocate 1.3G of RAM. I have 4G in my Macbook and assigned 1.3G to the Fusion 2.06 VM. I have no complaints and feel it is optimal. I think it ran worse when I allocated 2G to the VM

I'll try 1.3 to see what happens here.

J.R. Miller

https://community.logos.com/discussion/comment/37392#Comment_37392

I downloaded A3 today and it's indexing (again). My big issue is how much of my processor it takes in doing that indexing. I would expect indexing to control the amount of CPU it uses to a reasonable amount...

Hi Steve, the expectation is reasonable, but not in Alpha. During the Beta testing for L4windows, we went through the same thing. As the program was stabalized, the developers were able to make huge improvements (at least 40% improvement between Beta 1 and Beta 7). So I imagine we will get there with the Mac version as well.

Ross Strader

https://community.logos.com/discussion/comment/37506#Comment_37506

Joe,

How does the current Alpha compare to the Beta you tested, i.e. Beta 1?

Is Alpha behind where the Beta was when you first saw it?

(I understand generally the Alpha-Beta process... I'm just trying to get a sense of how behind the Alpha is to a Beta product)

Thanks,

Ross

J.R. Miller

https://community.logos.com/discussion/comment/37781#Comment_37781

Is Alpha behind where the Beta was when you first saw it?

Good question.

By the time we started Beta 1, the interface and features were well developed. The Beta process was focused on:

Refining the indexing process (which from Beta 1 to release probably doubled in speed)
Fine tuning the interface
Improving the home page
LOTS of feedback on the features that were there and what we wanted that wasn't there.

According to Bob P., the L4mac was in development concurrently with L4win. L4mac and L4win share the EXACT same code base, so every feature currently in the windows version IS already in our Alpha. One of the reasons I wanted to Beta the windows, was that I knew my input would have some influence on the Mac side.

There are two benefits, as I se it so far to being second.

First, our Alpha is already farther along than most Alpha projects in that it has a stable code base and the feature set is already highly developed. That is one reason why any settings or work you do in the L4win version will already synchronize with the mac Alpha... we just can see a lot of it or work with it.

Second, I have already noticed several improvements over the L4win version. Some of the biggest complaints and suggestions from the windows Beta tester were not implemented due to the time constraints of the release date. However, I have noticed that the Mac developers have taken advantage of the Beta process. They are not designing this to be the same as the Windows version (although I think they will be 95% similar), but they are building on the L4win experience and making improvements. I have posted some screen shots noting a few of these examples that I have seen.

The down side?

Well, I have to wait to use all the great features I tested out in windows. That is a bummer. Then again, I know what is coming, so I am excited to contribute to the process and hopefully speed things up with good bug reporting. The more bugs we test and find, the faster our Alpha will make it to production... and that would be a good thing!

Is that what you were asking for Ross?

J.R. Miller

https://community.logos.com/discussion/comment/37781#Comment_37781

Oh, maybe I should add, indexing is painful in Alpha and it was painful in the first Beta. However, at least our Alpha indexing is incremental, so if the process is disrupted, L4mac does not have to start over completely. That feature was not in L4win when it was released and I don't even know if it is in there now. So once they get the bugs fixed and stable, our indexing for Mac should be ahead of the game.

Ross Strader

https://community.logos.com/discussion/comment/37823#Comment_37823

Joe,

Great answer. That is exactly what I was looking for. I am just trying to get the big picture.

I too have seen the syncing from the L4win and L4mac. That is cool. I am also impressed with the speed of the program in responding to search, passage guide, etc. (when it doesn't crash).

So, I'm excited. I'm playing around on the L4win through parallels and then trying to see what is possible on the mac side.

Thanks for the thorough answer.

J.R. Miller

https://community.logos.com/discussion/comment/37834#Comment_37834

any time brother :-)

Dan Aikins

https://community.logos.com/discussion/comment/34216#Comment_34216

I've tried looking for the Indexer.log on my computer, but I can't find it. I searched the path you gave me and it wasn't there. I also checked under the Macintosh HD>Library... and it wasn't there either. I even searched with Spotlight and nothing shows up. Any ideas what is going on there?

Wes Saad

https://community.logos.com/discussion/comment/37823#Comment_37823

Oh, maybe I should add, indexing is painful in Alpha and it was painful in the first Beta.

Indexing is far more painful in the Alpha than it was in the Beta, at least with A3. With A1 I was able to complete indexing. With A3 I've yet to complete. Running on two machines, neither one has ever finished indexing.

J.R. Miller

https://community.logos.com/discussion/comment/38906#Comment_38906

Of course it is "more" painful Chris. That was not the point. The point is that Beta 1 improved as the developers improved the process. So we have hope that moving from Alpha through Beta through RC that the process will also improve.