I noticed that when Logos4Indexer kicks on, it makes my quad CPUs scream! I have hardly anything else running and it tosses my CPUs up to over 75deg (C).
Is there anyway you-all could help this run cooler?
Thanks.
I direct a household fan at my Laptop to stop it shutting down!
My Desktop handles it quite well. But you can install more fans in its case or get a more efficient after-market CPU cooler.
John,
An idea you might like to test, if you are using a recent version of Windows. (I am using Vista)
Please NOTE: My comments are NOT official and its possible that the Logos support team will advise against what I am about to suggest.
If this is your only PC, and you cant use Version 3 as an alternative, maybe best to leave this alone. Up to you, but it would be good to see feedback on this from others.
The warnings from the Beta Forum make a good point: http://community.logos.com/forums/t/8883.aspx
Anyway, the idea for consideration:
( I started an index run with "rebuild bible index" to get something running. As expected, it pegged CPU0 and CPU1 to max on my dual-cpu-code laptop using an Intel Centrino. )
1) I used Task Manager to find the Logos4Indexer.exe task.
2) Using right-click, I changed the priority on the task from "Normal" to "Below Normal".
3) From the same right-click, I changed the processor affinity from using CPU0 and CPU1, to only use CPU1 only.
In your case, if you turned 1, 2 or 3 of your CPUs off, the CPU die as a whole would run cooler (I guess), but the single core would continue to run at near 100%. Of course, it will take longer to complete too. However, you will have a "faster", more responsive system I expect.
My system is still running the index now, claiming 32 minutes still to go.
Possible outcomes:
A) This might help, for those willing to use it. If there is merit, Logos could add a setting to control priority and processor affinity into the program, for the indexer process.
2) This will corrupt my indexes, and I will need to run it all again, without messing around with the internals of someone elses application.
For anyone that has no idea what I'm talking about here, please leave this alone and dont mess with it OK.
Wait and see what others, and the Logos techs say before messing with stuff.
Regards,
Jim.
Bradley responded (bottom of p1) to this same suggestion in another thread http://community.logos.com/forums/t/13783.aspx particularly with respect to priority.
Dave,
Well spotted. I had not seen that thread before. YES - the question was well addressed in that other post. (But no final solution)
OK then - so the Indexer starts a low priority thread for each and every core you have.
So, my idea above, will still start 4 of them on a Quad, and then run them on less than 4, so it will take much longer !!!
HOWEVER, it still might be a good option for those that are having overheating issues.
If Logos has the Indexer code (rather than using something prebuilt from sqllite etc), then if there was the need or interest, they could add a "Indexer Max CPU%" setting. This would idle each thread for x units of time every y units of work. It could keep track of cpu usage, and sleep a while after each unit of work. Clearly, most users might want to always leave it on 100%, but it might be a nice option given than a major index run is 4-8+ hours or so for some users and systems.
It would have two uses:
1) Make the system a little more responsive, rather than pausing the indexer for x hours so it does now.2) Manage CPU temp such as reported in this thread and the 13783 one, re systems shutting down with heat issues.
A hardware cooling solution is generally more satisfactory, especially with recent Intel i5/i7 multi-cores which manage thermal output depending on the load by varying the CPU clock speed (turbo boost) eg. from a nominal 1.6 GHz to 2.8 GHz, or 2.66 GHz to 3.33 GHz. If 4 cores are running at 1.6 GHz restricting the load to 2 cores may allow CPU speed to increase to 2.8 GHz whilst pumping out the same amount of heat! So the cooling problem has not gone away and indexing will take longer. Of course you could turn off Turbo Boost, but would you want to do that for one application?
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
