Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
If windows server has a limitation of 9 engines...
Why QMC lets us configure unlimited number of engines?
Here is the information you are looking for. Please backup your registry before you make any changes.
memory Heap Registry change:
Change the registry setting:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows
Change the GDI and User handle max count in the registry to SharedSection=1024,20480,2048
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16
Default is 1024,3072,512 in x86 or 1024,20480,768 in x64
Read more on http://blogs.msdn.com/ntdebugging/archive/2007/07/05/desktop-heap-part-2.aspx
Read more about Desktop Heap on:
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx
Desktop Memory Heap Registry change:
Change the registry setting:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows
Change the GDI and User handle max count in the registry to SharedSection=1024,20480,2048
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16
Default is 1024,3072,512 in x86 or 1024,20480,768 in x64
Read more on http://blogs.msdn.com/ntdebugging/archive/2007/07/05/desktop-heap-part-2.aspx
Read more about Desktop Heap on:
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx
There is a windows configuration available from support -- and here on the forums -- that provides for greater than 9 engines.
-Rob
Do you have this link to the forum? My server has 48 cores and 256Gb, and I can run just 9 concurrent engines. I 'm wasting server.
Thanks
I can't find the article. Please contact Support.
-Rob
Here is the information you are looking for. Please backup your registry before you make any changes.
memory Heap Registry change:
Change the registry setting:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows
Change the GDI and User handle max count in the registry to SharedSection=1024,20480,2048
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16
Default is 1024,3072,512 in x86 or 1024,20480,768 in x64
Read more on http://blogs.msdn.com/ntdebugging/archive/2007/07/05/desktop-heap-part-2.aspx
Read more about Desktop Heap on:
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx
Desktop Memory Heap Registry change:
Change the registry setting:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows
Change the GDI and User handle max count in the registry to SharedSection=1024,20480,2048
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16
Default is 1024,3072,512 in x86 or 1024,20480,768 in x64
Read more on http://blogs.msdn.com/ntdebugging/archive/2007/07/05/desktop-heap-part-2.aspx
Read more about Desktop Heap on:
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx
Thanks Bill!
-Rob
Thanks Bill, this configuration is sufficient to put for example 48 concurrent engines ?
Or these parameters are proportional?
It is something you will have to play with. I don't think running 48 concurrent engines would be a good ideal. You have to look at the memory that is used by each task and then save resources for the OS and QVS.
Bill
Hi
As I now ,distribution service himself is controling quanttity of paralel reloads (by setting in QMC). For example if you start 40 tasks at one time but setting is 9 - at same time will be working only 9 but all 40 tasks will be done.
And these 9 tasks will use significiant resources anyway.
Am I true, experts ?
Best regards
Hi,
I have the same problem too.
I'm using 24 cores, 64 bits, 64GB memo.
Initially i set "Max number of simultaneous QlikView engines for distribution:" to 15 in QDS.
and now i set it to 24-1 = 23. still the same result.
What are the risks of changing the heap registry?
Any other way of doing it?