Fragment cache

[tommy351]

Add fragment cache to improve the performance of file generating. This concept is stolen from Ruby on Rails. The cache will be only enabled in generating mode.

New helper: fragment_cache(id, fn)

<%- fragment_cache('footer', function(){
  return '<footer></footer>';
}); %>

Partial cache

A new option cache will be added to partial helper. This is a shortcut to fragment_cache helper. For example:

<%- partial('footer', {}, {cache: true}) %>

yields:

<%- fragment_cache('footer', function(){
  return partial('footer', {});
}) %>

The effect of fragment cache is remarkable. I used fragment_cache helper in sidebar to reduce database queries. It only took less than 10 seconds to generate 1000+ static files. The original elapsed time is 10 minutes, which means is at least 60x faster.

[sergiolepore]

Great! :)

[floriancargoet]

What about caching the article content on disk? Most of the time, only the sidebar changes.
Only the new posts and the changing parts would be rendered to html and then everything is combined.

[tommy351]

@floriancargoet This is a great idea. But it may be difficult to implement.

[floriancargoet]

I thought of that because that how make works. It checks the last modified date of source files and recompiles only the modified ones (since last compilation), then everything is "concatenated" with the linker.