Lazy evaluation of extractor values for ThymeleafTemplateEngine #471
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed a strange behaviour baking a site using thymeleaf template engine.
https://gitlab.com/devlug/devlug-web
It was awful slow.
I took a look at the memory consumption with visualvm.
When it hits the 500 MB mark the rendering process starts.
With the applied fix the overall bake time goes down do nearly 8 sec.
And the memory consumption looks much better, too.
I had to update the gradle wrapper as bintray dropped TLS 1.0/1.1 support, which caused the java 7 build to fail on travis and appveyor. See https://jfrog.com/knowledge-base/why-am-i-failing-to-work-with-jfrog-saas-service-with-tls-1-0-1-1/
An update to orientdb slipped into this pr. Shall I revert it?