The document you mentioned does provide steps to enable/disable NUMA using a soft-switch (in Settings.ini). However you have to use a Settings.ini parameter only if the server platform BIOS doesn't provide a switch to do this when booting up.
For example, Hyper-Threading is a cpu setting. IMHO you cannot let QlikView disable/enable Hyper-Threading because when QlikView launches it's already too late to change the processor mode-of-operation.
See you server BIOS help for information on how to configure the cpu and motherboard settings.
Thank you Peter.
One more question, I have other applications which runs based on IIS in the same QlikView server. Can you please tell if disabling NUMA will have any impact over other applications running based on IIS.
My QlikView server is Single machine with IIS. Please advise.
and if in case NUMA cannot be disabled, "EnableNumaRoundRobin=0" has to be written in "setting.ini" under "QlikViewServer" folder.
EnableNumaRoundRobin=0 is defaulted and means disabled functionality.
EnableNumaRoundRobin=1 means enable functionality which should be used for servers where NUMA cannot be disabled in the hardware
I'm not an IIS user, so I don't really know from experience whether disabling NUMA will adversely affect IIS operation. But I guess it will not. IIS is a multi-threaded application with low memory requirements (in QlikView's case). I think it will be hampered more by disabling Hyper-threading.
Forget about manipulating NUMA in Settings.ini. the document you linked to clearly states that as of QV11.20SR2, QlikView Server automatically disables/ignores NUMA based on what is best for QlikView performance. This also applies to all later QVS releases, including the SR7 release you seem to be using.