I have A12. The Logos4Indexer in the Activity Monitor is taking between 50-95% of the CPU, which seems pretty excessive. Anyone else having this happen?
For the first 10-15 minutes on A11 I would get CPU utilization around 150% (100% being 1 full core in a multi-core system.) A12 appears to do the same thing but I haven't used it enough to be absolutely sure.
This is normal. When I installed A-5/6 (I forget which one I started with) it ran in this range for some time. Indexing on my Windows machines also used mid to high 90's of my indexer for the majority of the index time. Just think, the indexer is reading your entire library and creating an index to support not just basic searches, but morph and beyond; that's a lot of information to get through!
Todd, indexing has not been optimized for the Mac. This will happen later in the development cycle.
indexing has not been optimized for the Mac. This will happen later in the development cycle.
Even when it is fully optimized, it will consume a fairly large fraction of the CPU while it is working. The optimizations will simply reduce the total amount of time that is required to complete indexing. As mentioned above, the Windows version similarly consumes substantial amounts of the CPU during indexing.
Consuming large amounts of the CPU to do actual work is not uncommon nor is it a bad thing. For instance, applying complex filters in graphics software or working with video will similarly consume substantial amounts of the CPU. High CPU usage is generally considered problematic when that CPU time is being spent frivolously.
Thanks for the clarification Cameron!
indexing has not been optimized for the Mac. This will happen later in the development cycle. Even when it is fully optimized, it will consume a fairly large fraction of the CPU while it is working. The optimizations will simply reduce the total amount of time that is required to complete indexing. As mentioned above, the Windows version similarly consumes substantial amounts of the CPU during indexing. Consuming large amounts of the CPU to do actual work is not uncommon nor is it a bad thing. For instance, applying complex filters in graphics software or working with video will similarly consume substantial amounts of the CPU. High CPU usage is generally considered problematic when that CPU time is being spent frivolously.
Is it normal to have a significant period of CPU utilization every time the application is opened? More specifically it seems to happen not on open but when I run the first passage guide. Subsequent runs in that session are fine but if I close the APP and start again the cycle begins anew.
Guide section generation is a fairly computationally expensive process for certain sections, so yes, I'd expect to see some substantial CPU utilization when opening guides. Again, the optimization goal here would probably be to reduce the total amount of time that we're consuming a substantial fraction of CPU so that the content is rendered more quickly.
Hi,
following this thread since installing logos 4 on my MacBook Pro (8GB ram, 500GB hd, 3.06 GHz Core 2 Duo), the machine has been running like the worst of my memory of windows machines! also, my HD seems to be constantly spinning and my time machine seems to do a 5GB back up every hour.
Having rebooted, the indexer is now working, again, and it tells me that it's got 3 hrs 27 mins remaining. Nothing has changed since the reboot, as far as i'm aware.
It's also absorbing up to 135% CPU time
I realise this is an alpha product, but can anyone tell me how to unintslall / remove these background processes until a more stable release is issued?
also how to remove what it's putting on my time machine?
thanks,
Joe
Joe,
I think that you are asking not to have the program!
The indexing and disc access is the program reading your resources and building the index that is personal to your library.
When it has finished it will make a real difference to the usability of the program.
May I suggest leaving it on overnight when you don't want to do anything else with the computer and letting it complete its work.
Once the long haul is over updates are much quicker.
Best wishes
Mike
Mike,I understand (and am really looking forward to being able to use the full capacity of the programme with indexing), and yep, your right I may have to uninslall the programme! I'm OK to wait until you optimise the indexing and address the time machine issue and it becomes more stable.having said taht, the indexer has stopped tho' and I've excluded the Logos4 directory from my Time Machine backups to see if this helps. I'll try to run it for anohter week or so...
I know you guys are working hard on this, no pressure from my end, I realise it's an alpha version!keep up the good work & sorry if i'm distracting you from more important matters!Joe
and I realise that you Mike may not be a developer but an enthusiastic walker in the darkness of the alpha verion like me... (only judging by your posts a much more experienced one!)
;-)
and I realise that you Mike may not be a developer but an enthusiastic walker in the darkness of the alpha verion like me... (only judging by your posts a much more experienced one!) ;-)
You can recognize Logos employees by the blue Logos icon under their avatars.
cheers Kevin
Logs would be helpful here. If the indexer is crashing before it finishes, any work it did prior to crashing is lost and it will attempt to start over from the beginning. There are instructions for enabling the most verbose logging and posting the logs in the FAQ linked in my signature. Once you get a completed index, it should stop trying to re-index constantly.
my HD seems to be constantly spinning and my time machine seems to do a 5GB back up every hour.
It's probably backing up the index, which is a single file that is almost certainly 4-10GB (depending on how many resources you own). During indexing, there isn't really a way around this. If Time Machine is attempting to backup hourly while indexing is going on, it's going to attempt to backup the index file each hour because the index file will change constantly during the indexing process. That particular behavior is unlikely to change, even in the final release.
And it's only stopping there because your MacBook Pro's CPU only has 2 cores; we'll use up to 4 cores when they're available (e.g. on a Mac Pro or new iMac). As I've mentioned previously in this thread, that's a feature, not a bug. Even in the final release, the indexer will be written to utilize as much CPU as we can. The optimizations will be focused around reducing the duration of indexing. High CPU usage is only a problem when/if a) it interferes with other work you're trying to do (see below for a solution to this) and b) no useful work is being done (e.g. a runaway process/infinite loop).
We've provided the "pause indexing for 4 hours" option for situations when the indexer is consuming so much of the CPU that it slows down your regular usage. Then, when you get to a point where you don't need those CPU cycles, let it resume indexing.
Cameron,
thanks for full reply - really helpful.
working well now - the problem was exacerbated by another bit of alpha software I was running, plus upgrading to Aperture 3 (didn't realise that face recognition was running in the background!!).
so with Logos, and this stuff, my MBP (deapite 8MB ram) was making a good fist of pretenting to be a PC, with lots of delays and spinning wheels...
looking forward to more developmenst on Logos 4. I'm new to the software so am only just beginning to figure out my way round... and as the mac version is still alpha, not sure the other videos will help?
keep up the good work!
