Renderer process priority

[joelhnatow]

Hi,

In my Windows application I'm spawning a separate sub-process for the CEF renderer. I'm trying to keep this sub-process running as a "Below Normal" priority class. The machine this application is running on is CPU constrained and I need to make sure the CEF / browser portion of things doesn't starve CPU cycles from the other processes running on this machine. I can set the process priority initially to Below Normal in my CEF renderer exe, but I noticed that it seems like somewhere under the hood this priority can be changed back to Normal. For instance, if I select an HTML drop down in the browser, the process is reverted back to Normal priority. Is there any way to prevent this process priority change from within CEF or is this within the Chromium guts?

Thanks!

Joel

[magreenblatt]

It would be within Chromium.

[joelhnatow]

OK, that's what I assumed. Thank you for the quick response and a great piece of software!

[HarmlessDave]

You might have already thought of this, but you could try using CEF render process events like OnBeforeNavigation to drop the priority back down again. If you can map out everything that is raising the priority you could optimize this to only lower the priority after you know it has been raised.

Another approach would be to find all the thread priority calls in the chromium code and comment them out. You'd probably need to re-do this every time you updated the source.