Engines for genius

[leocvaz]

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

Why QMC lets us configure unlimited number of engines?

[#2]

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

[#3]

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

[Emmanuelle__Bustos]

Hi Bill Britt

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

[#5]

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?

[Anonymous]

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

[#7]

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.