You gotta be kidding me

Ok, bought and downloaded one (1) new book, , just one.

Processors sitting at 150% again to reindex whole deal, been that way for a while, will probably take 30 to 45 min of processors being hammered, heat up, fans wide open.

Someone recently posted in another thread that Logos cannot "physically " harm your computer.

I do not believe this to be accurate: When a program is written in such fashion as to overtax the processor section os a computer, great heat is created, high heat levels lower the life expectancy of the components .

I was in the Music Industry for 34 years as an Audio Engineer, thus I know what high heat levels does to electronics, its not good.

So-Really! One book = re-index at 154% of processor for 45 min and this is good code? Really?

I don't think so Tim!

This really does need to be addressed.

Thanks

Find more posts tagged with

Comments

fgh

Tip on how to index as fast as possible: http://community.logos.com/forums/p/45783/342304.aspx#342304.

Keep Smiling 4 Jesus :)

Processors sitting at 150% again to reindex whole deal, been that way for a while, will probably take 30 to 45 min of processors being hammered, heat up, fans wide open.

Apologies: did not check processor usage while 6 resources were updated today; took 27 minutes to merge postings.

Edit: while watching indexer progress for a new purchase, noticed Logos4Indexer usage vary from a few % to 188 % along with Finder usage varying from 0 % to 100 %. While indexing in progress, had Console utility open to watch Indexer.log file.

Am aware Logos has slowed down indexing speed on Mac => Logos 4.5 Beta 12 Library Indexing Speed Regression - Mac is Slow

I do not believe this to be accurate: When a program is written in such fashion as to overtax the processor section os a computer, great heat is created, high heat levels lower the life expectancy of the components .

Prudent to check for heat dissipation issues (e.g. feels hot to touch) implies need for additional cooling; personally have used many fans.

Keep Smiling [:)]

Wes Saad

So-Really! One book = re-index at 154% of processor for 45 min and this is good code? Really?

One comment on 154% - apologies if you know this already. My understanding is that values over 100% are not really pushing your processor farther than they are supposed to go but reflects multi-core usage. 100% would be wide open on one core; over 100% means more than one core is being used.

Still an aggravation to have so much indexing, just wanted to clarify about that value.