Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE

Native Cache Warming (with multi-node management)

simonaubert
Partner - Specialist II
Partner - Specialist II

Native Cache Warming (with multi-node management)

Hello,

As of today, the cache warming (loading an application in RAM from disk to gain some time at app opening) can be done by non-supported tools. It's also not trivial to use. So I would want a native cache warming feature, taking into account the multi-node deployment (I only want to put in cache some big app on the nodes that I use for front-end user). Basically, a checkbox on the app or task like "stay in Ram after reload". That sounds pretty simple, no?

image.png

 


Best regards,
Simon

Bi Consultant (Dataviz & Dataprep) @ Business & Decision
Tags (2)
6 Comments
rzenere_avvale
Partner - Specialist II
Partner - Specialist II

I agree for the basic version.
All additional features that the other tools give us (cycling through sheets, values of a field, ...) should be kept on those tools, as each customer probably has specific requirements (so, let's keep it simple).

Riccardo

fmarvnnt
Partner - Creator III
Partner - Creator III

Why in QlikView and not in Qlik Sense?

 

Thomas_Hopp
Employee
Employee

Hi @simonaubert thank you for submitting this idea and sorry for getting back to you with a delay.

We are currently investigating the possibility of support "App preloads" into memory. The way how I / we are understanding your idea, this would be covered by it, right ? Meaning if you can configure the time when you want an App to be preloading an App into memory, would that solve your scenario ?

Best regards,

Thomas

Status changed to: Open - Collecting Feedback
simonaubert
Partner - Specialist II
Partner - Specialist II

Hello @Thomas_Hopp  Thanks for getting back, I really appreciate.

I would have maybe two different cases :
-stay in ram after reload (because I don't know when the application will be reload : it's triggered through api or whatever like the reloading time can vary a lot).
-come in ram at a defined hour (because the app is reload at 6 am and the user needs it at 9 am, I don't want to consume ram for nothing during the morning mass reload)

Also for the end : move out of ram after 6 hours or at 7 PM.

Best regards,

Simon

Meghann_MacDonald

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.

Ideation
Explorer II
Explorer II
 
Status changed to: Closed - Archived