THANK YOU - Indexer Now Scheduled at LOW Priority
Thank you! The last several resources I've added have resulted in minimal (few seconds only) times when the laptop is too busy (mostly disk?) even to respond to the touchpad.
Why? Logos now runs the indexer at low priority, & I haven't had to set it to low. So far, the indexer is robust enough that this has never caused a problem to Logos, & it's been a huge blessing to my ability to do anything else....
So, THANK YOU!!!! [8-|] [:D] [H] [8-|]
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB
Comments
-
Interesting. I'm curious to see how that plays out on various systems. I typically set the indexer to Below Normal. I don't think I've ever bumped it down to LOW. Below Normal has seemed enough to bump the IO Priority down which I think is the bottleneck, at least on my system. I wonder how it affects slower processors... Hopefully, this will improve experience for everyone. Thanks Logos for looking into this.
0 -
Bill, are you running the Windows version? I recall Bob saying in the big, long "Logos 6" thread that they didn't have this option in Windows.
Bob Pritchett said:On Windows we've been looking at managing process priority, and it looks like the only options are "too much" and "too little." Intense use for a few hours, or low level use that takes days. There doesn't seem to be a good intermediate step.
I'll be very interested in receiving this update if they figured it out.
0 -
William Gabriel said:
Bill, are you running the Windows version? I recall Bob saying in the big, long "Logos 6" thread that they didn't have this option in Windows.
Bob Pritchett said:On Windows we've been looking at managing process priority, and it looks like the only options are "too much" and "too little." Intense use for a few hours, or low level use that takes days. There doesn't seem to be a good intermediate step.
I'll be very interested in receiving this update if they figured it out.
I'm running W8.1 native, L5 latest beta....
Total config below in signoff. :-)
(Posting in W8.1, IE 11, & that's the only emoticon I have. [:)] )Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Randy W. Sims said:
Below Normal has seemed enough to bump the IO Priority down which I think is the bottleneck, at least on my system.
In my testing on Windows 8 x64, I never saw the I/O Priority being reduced (according to Process Explorer) when using Task Manager to change the process priority.
How were you verifying that I/O Priority was reduced? (I want to make sure I didn't miss anything.)
0 -
Bradley Grainger (Logos) said:Randy W. Sims said:
Below Normal has seemed enough to bump the IO Priority down which I think is the bottleneck, at least on my system.
In my testing on Windows 8 x64, I never saw the I/O Priority being reduced (according to Process Explorer) when using Task Manager to change the process priority.
How were you verifying that I/O Priority was reduced? (I want to make sure I didn't miss anything.)
It's much more likely that I'm missing something. I was basing that off the information I found when researching IO Priority (though there doesn't seem to be much documentation out there).
- Everything I read indicated that IO Priority was directly affected by Process Priority.
- On my system, Logos never comes close to maxing out CPU.
- It does bog down on IO (7200 RPM HDD).
- System responsiveness is often extremely sluggish during portions of indexing.
- System responsiveness improves greatly when reducing Process Priority to Below Normal or LOW.
I added up the above and ASSUMED it was likely attributable to IO Priority. I didn't think to check Process Explorer to verify; didn't remember that setting to view IO Priority, but checking now I see the same result you see. I also tried another cool utility, Process Lasso, which shows the same results.
I'm not sure now where the improvement comes from, though I still suspect it's IO related, but it is definitely an improvement.
0
