Cache rendered template
See original GitHub issueSeems like Fue is compiling the template each time I call it (I’m using fromText
), even if it doesn’t change (except the data). This generates a lot of unneeded memory traffic which I’d like to avoid. Is there any way to reuse the compiled template?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
go - What is a template cache?
The template cache exists so that templates have to be compiled only once. Without it, the same template(s) would have to be compiled...
Read more >Documentation: Ultimate Guide to Template Module Caching
When caching is enabled, and Movable Type no longer needs to parse, compile and render the contents of a template module, the number...
Read more >Frequently Asked Questions — Jinja Documentation (3.1.x)
Rendering a template becomes as close to executing a Python function as possible. Jinja also makes extensive use of caching. Templates are cached...
Read more >Partial Caching | Silverstripe CMS Documentation
Partial template caching is a feature that allows caching of rendered portions a template. Cache block conditionals#. Use conditions whenever possible. The ...
Read more >Build Faster Websites with Craft CMS Template Caching | Blog
As you can imagine, a very complex or content-heavy page will probably require many more database queries to render everything. Caching a section...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
PS: @Dzoukr thanks for a nice codebase that works OOTB when using .NET Core on Linux!
Hi @petejohanson & @megafinz, I just merged changes from PR. Let me check few tests and we can publish new version. I agree with @petejohanson that it is subtle change and behavior should be actually like that from very beginning.