topic Re: Engines for genius in QlikView

Engines for genius

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

If windows server has a limitation of 9 engines...

Why QMC lets us configure unlimited number of engines?

Re: Engines for genius

rwunderlich — Tue, 21 Aug 2012 15:00:58 GMT

There is a windows configuration available from support -- and here on the forums -- that provides for greater than 9 engines.

-Rob

Re: Engines for genius

leocvaz — Tue, 21 Aug 2012 21:17:30 GMT

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

Re: Engines for genius

rwunderlich — Wed, 22 Aug 2012 01:33:50 GMT

I can't find the article. Please contact Support.

-Rob

Re: Engines for genius

Bill_Britt — Wed, 22 Aug 2012 01:53:13 GMT

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 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

Default is 1024,3072,512 in x86 or 1024,20480,768 in x64

Re: Engines for genius

rwunderlich — Wed, 22 Aug 2012 02:42:01 GMT

Thanks Bill!

-Rob

Re: Engines for genius

leocvaz — Wed, 22 Aug 2012 15:09:55 GMT

Thanks Bill, this configuration is sufficient to put for example 48 concurrent engines ?

Or these parameters are proportional?

Re: Engines for genius

Bill_Britt — Wed, 22 Aug 2012 15:30:49 GMT

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

Re: Engines for genius

Tue, 28 Aug 2012 10:26:30 GMT

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

Re: Engines for genius

Thu, 25 Oct 2012 07:06:37 GMT

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?

Re: Engines for genius

Tue, 15 Jan 2013 10:21:41 GMT

Hi Leonardo,

I am currently setting up some similar (60 core) servers and was wondering what your findings on the heap size settings were?

Thanks,

Graeme

Re: Engines for genius

Thu, 17 Jan 2013 11:28:34 GMT

I have done some testing, and was getting COM errors with the non interactive heap size set to 2048 when I had 30+ engines running in parallel. By increasing the non interactive heap to 6144 I have managed to run 40 engines in parallel and am not seeing any COM issues logged (QV11 SR2).

Cheers,

Graeme

Re: Engines for genius

Emmanuelle__Bustos — Thu, 14 Feb 2013 18:06:11 GMT

Hi Bill Britt

These change in the registry applies for QVS 10 as well or is only for QV11?

Re: Engines for genius

Tue, 09 Feb 2016 11:11:11 GMT

Hello,

Recently we changed the Memory Heap settings mentioned above for a 40-core Windows Server 2008 R2 Enterprise. The server failed to restart with a Blue Screen and we had to revert the changes. Will the above change work in this Server?

Re: Engines for genius

Anonymous — Sat, 02 Apr 2016 01:08:16 GMT

Graeme, did you attempt to run more than 40 and got errors and then reduced it to a 'safe' level of 40? Were those tasks connecting to a database i.e. did a QVConnect64.EXE or QVConnect32.EXE process also run alongside the QVB.EXE engine process?

I ask since Desktop Heap is a Windows process consideration and since tasks that connect to a database trigger the launching of 2 processes instead of just QVB.EXE on its own this might impact that maximum allowed based on the registry setting.

In my quick tests each process consumes around 80K of non-interactive Desktop Heap memory so your numbers also make sense e.g. 6144K / 40 = 154K / 2 processes = 77K

Re: Engines for genius

Mon, 04 Apr 2016 06:45:19 GMT

Hi Steve,

The tests I ran were just qvw's with auto generation of a large number of records (to stress the CPU/RAM). I did not have any DB connectivity (it's a good point about the extra overhead on the heap for qvconnect processes). The servers I was testing had 40 physical cores, so that was as far as I went with the number of parallel qvb processes (I would not attempt to run more qvb processes than there are physical cores). We have been running with 40 in live for a long time now without issues, although I would say on average we only ever have about 20-25 jobs actively running in parallel.