topic qvb.exe Lowering CPU Priority in QlikView

qvb.exe Lowering CPU Priority

Anonymous — Mon, 26 Jan 2026 18:19:17 GMT

We have both QV Server & Publisher running on the same. Yup I know that is not recommended, but unfortunately that is where we are.

Does anybody have any experience on lowering the qvb.exe process CPU priority ?

On the web I have found a utility called Process Tamer and am considering it to lower CPU priority for qvb.exe and force qvs.exe to higher priority, would this be wise ?

Has anyone used any other methods ?

Best Regards, Bill

Re: qvb.exe Lowering CPU Priority

Thu, 17 Apr 2014 15:18:47 GMT

there are a tool called QvAffinityConfigurator,

Regards

Michael

Re: qvb.exe Lowering CPU Priority

Anonymous — Thu, 17 Apr 2014 16:56:19 GMT

Michael

Many thanks for pointing me towards QvAffinityConfigurator. I have found it on github.com.

I am on leave next week, but will certainly have a look at it after that.

Best Regards, Bill

Re: qvb.exe Lowering CPU Priority

woshua5550 — Mon, 09 Oct 2017 06:48:59 GMT

Hi Bill

did you lower the CPU priorty successfully ? if you do , how do you do that ?

thanks

Re: qvb.exe Lowering CPU Priority

Peter_Cammaert — Mon, 09 Oct 2017 08:14:48 GMT

In C:\ProgramData\QlikTech\DistributionService\Configuration.xml, look for a QVBConfig line. Change the value for CPUPriority at the end of that line (shut down the QDS service first).

By default it is already set to "Low" and IMHO you can't go any "Lower".

Changing this configuration option may easily lock-up your QlikView server. Use at your own risk.

Re: qvb.exe Lowering CPU Priority

Anonymous — Mon, 09 Oct 2017 09:15:22 GMT

Since April 2014 when I was messing about with this on QlikView we have now upgraded to Qlik Sense, and to be honest I cannot remember the details - Apart from that the end results were neutral, as in nothing broke but I got no tangible positive improvements.

I would agree with Peter's recommendation for caution, and since for me it made no discernible difference to me maybe you should be prudent and avoid wasting time with it.

I think the bottom line is to follow best practice recommendations and accept the fact that if server ~~are overloaded then the best way forwards is to replace / upgrade them appropriately.~~