Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
i want to know if there is a way to limit the use CPU cores for the publisher .exe files.
After migrating to Qliview 12.3 the publisher uses much more CPU than before.
in some time ranges Publisher takes 90-100% of the CPU. That leads to Performance degrade on users site.
My wish would be to say that next two files can only use 60% of the CPU cores.
Thanks for any help
regards
tim
The only way to impact things is via the following two settings in the 12.30 and later tracks:
<!-- If the CPU usage % goes above this value the machine is considered overloaded and no new tasks will be started. -->
<add key="CpuOverloadLimit" value="75"/>
<!-- If the memory usage % goes above this value the machine is considered overloaded and no new tasks will be started. -->
<add key="MemoryOverloadLimit" value="90"/>
This is really only going to impact whether a task is able to start though, but that might have a positive impact as if you are running too many concurrent tasks, that is likely the real culprit. I would venture the correct solution though is to use a separate server for the Publisher services, this way you do not impact the QVS and the user experience... A virtual machine with the correct resources allocated where the host machine is not oversubscribed would work well for Publisher, it would not necessarily need to be a physical server. About the best guidance I can give you.
Here is a link to a doc the engineers put together last year on scaling Publisher too:
Regards,
Brett
The only way to impact things is via the following two settings in the 12.30 and later tracks:
<!-- If the CPU usage % goes above this value the machine is considered overloaded and no new tasks will be started. -->
<add key="CpuOverloadLimit" value="75"/>
<!-- If the memory usage % goes above this value the machine is considered overloaded and no new tasks will be started. -->
<add key="MemoryOverloadLimit" value="90"/>
This is really only going to impact whether a task is able to start though, but that might have a positive impact as if you are running too many concurrent tasks, that is likely the real culprit. I would venture the correct solution though is to use a separate server for the Publisher services, this way you do not impact the QVS and the user experience... A virtual machine with the correct resources allocated where the host machine is not oversubscribed would work well for Publisher, it would not necessarily need to be a physical server. About the best guidance I can give you.
Here is a link to a doc the engineers put together last year on scaling Publisher too:
Regards,
Brett