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?
Best regards, Simon
Bi Consultant (Dataviz & Dataprep) @ Business & Decision
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).
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 ?
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.
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.