topic Re: RAM spike creating first connection in Qlik NPrinting

RAM spike creating first connection

markodonovan — Fri, 13 May 2016 08:16:51 GMT

Hi there,

Just started a trial of Nprinting 17.

I am getting a spike in RAM generating the cache for my first connection.

Is this normal ?

Is there anyway to retrict the RAM Nprinting uses ?

I am also getting the following message popup.

Thanks

Mark

Here is the last few lines of the nprinting_engine log file:

[Engine.Navigator.QlikView.IQlikViewNavigatorFactory],Engine.Navigator.QlikView.QlikViewNavigatorMetadata][] with length 1

2016-05-13 09:07:22,252 [7] WARN Engine.Navigator.QlikView.QV11.QlikViewNavigator.[8372]::navigator=qlikview;documentpath="d:\QlikView\QDF\UAT\Hireman\1.Application\OPERATIONAL KPI\Operational KPI2.qvw" - QlikView CPU monitor: process seems stuck due to cpu usage of 61.92 % in 1089ms. Waiting for idle for 2000ms

2016-05-13 09:07:26,466 [26] INFO Engine.Navigator.QlikView.QV11.QlikViewDocument.[8372]::navigator=qlikview;documentpath="d:\QlikView\QDF\UAT\Hireman\1.Application\OPERATIONAL KPI\Operational KPI2.qvw" - Content request 64ee360a-968c-425f-9757-d90c7adcea79: resolution started

Re: RAM spike creating first connection

Fri, 13 May 2016 08:38:53 GMT

Above N printing log shows memory using peak level , and while fetching all Operational KPI2.qvw objects[charts, tables, kpi's, qlikview app Objects] to Nprinting server its also add up Usage ram . For clearance of usage RAM means Srop and restart all services of Qlikview and Nprinitning

Re: RAM spike creating first connection

markodonovan — Fri, 13 May 2016 13:36:07 GMT

Thanks for the reply srinivas,

I'll give this a go when possible.

Mark

Re: RAM spike creating first connection

markodonovan — Mon, 16 May 2016 14:00:06 GMT

Hi all,

So far I have move the engine to a different machine as it seems to use as much CPU as it can.

I am seeing a CPU of 80%+ when generating the cache for some documents.

Mark

Re: RAM spike creating first connection

Daniel_Jenkins — Mon, 16 May 2016 22:36:02 GMT

Hi Mark,

First, your message popup (Interactive Service Detection) concern. A Windows service called "Interactive Services Detection" notifies the user that a program window has been opened in an isolated session when the NPrinting engine service opens a QlikView Desktop instance to generate the connection cache. This is not an error message. This message does not have any effect and it is just informing you that there is an interactive service running. You can safely ignore this or stop and disable this service using services.msc but this will stop all ISD messages not just the ones triggered by NPrinting. I would simply ignore it rather than disable it.

Regarding your 80%+ CPU usage statement, I'm not sure if you consider this a good or bad thing. I would say using all possible resources (CPU and memory) to get the job done quicker is good rather than allowing some resources to sit idle doing nothing. If there are no other side effects I would consider this a good thing.

HTH - Daniel.

Re: RAM spike creating first connection

markodonovan — Tue, 17 May 2016 07:28:30 GMT

Thanks for the info Daniel,

I have moved the engine to another machine while testing (only 10GB RAM).

So far I have had no trouble generating a cache for a 5MB qvw

but not been able to generate a cache for a 800MB qvw.

I'll be testing this more today.

Mark

Re: RAM spike creating first connection

Stephen_Jasionowski — Tue, 17 May 2016 13:16:51 GMT

Mark -

Do you have any selections locked when the QVW is opened? By default, NPrinting 17 will clear all selections in the QVW in order to be able to cache the full object list. We have observed other cases where the RAM spikes due to the locked selections being cleared at the start of the process.

Re: RAM spike creating first connection

markodonovan — Tue, 17 May 2016 13:31:04 GMT

Hi Stephen,

Thanks for the reply. That is quite possible the issue.

The next thing I was going to try was using publisher to create a smaller version of the document just for nprinting.

Mark