Logos.exe process priority isn't elevated after updates

After installing Beta 3, another 2 updates were installed (small DB update, and a few resources). In each case, after the update & indexing, Logos.exe remained at LOW priority. Restarting Logos, it opens at Normal priority.

I don't think this occurred on Beta 2. The Normal priority was restored after updates.

Find more posts tagged with

Comments

Dave Hooton

Concur!

Bradley Grainger (Logos)

Thanks for noticing this. (I learnt something new today: "The idle-priority class is inherited by child processes."; http://msdn.microsoft.com/en-us/library/windows/desktop/ms686219.aspx). This will be fixed in the next beta.

Randy W. Sims

Thanks, Bradley.

The changes in priority of the indexer seems to be working very well on my desktop and tablet. It's not noticeably slower and system responsiveness is much better.

I'm not sure if it's come up before, but is there any merit in having a startup app or service (not sure if a service can be used for user level apps) to check for updates so that updates can (at user discretion) be downloaded and indexed even when Logos isn't running?

Lee

The changes in priority of the indexer seems to be working very well on my desktop and tablet. It's not noticeably slower and system responsiveness is much better.

It's about time! [:)]