Restarting Qlikview Services daily?

[#1]

Hello,

I'm seeking a bit of advice/steer in relation to whether we should restart Qlikview services on a regular basis. We have encountered issues recently where the memory is consistently at 75% of total memory on the server and this remains the case overnight when users rarely use any application. There are also regular reloads that fail every day which I'm confident are tied to the memory issue. The document timeout is currently sitting at 6 hours and by changing this timeout it could help the memory situation.

In an organisation I previously worked at there was a scheduled task to restart all the Qlikview services overnight and there were rarely any memory issues encountered and very few reloads that failed. I suppose my question is do we implement restarting the Qlikview services overnight, or change the document timeout first and evaluate the affect of this before going for the overnight restarts? Or is there something else that needs investigated?

For information we use Qlikview 10 SR3.

Thanks,

Ralph

[danielrozental]

Ralph, if you can live with it I would definitely recommend the daily service restart, before the reloads.

QlikView will consistently use 70% of the memory to store results cache.

You might also want to consider moving reloads to a separate server, a Publisher license is needed for that.

[bnichol]

Ralph,

We've been doing daily Server restarts for years and it has been helpful minimizing memory issues.

Also, your idea about reducing the document timeout should help.  We've recently reduced the timeout to 30 minutes.  Previously it was as high as 8 hours, but increased data size and number of users precipitated the change.

Good luck,

B

[Bill_Britt]

This would be normal. Your Working Set Limit is set by QVS as 70% - 90% or total memory.

Bill

[#5]

Many thanks for all the comments. It's given me the reassurance I need to implement the daily restart of Qlikview services.

Ralph