fix(velocity): Memory and sync issues #34046
Description
Problem Statement
There are a number of improvements we can make to velocity to improve its memory footprint. For starters, we do not even stream our responses, we turn them into String buffers and then send them.
Additionally, there are a number of places where we can use ThreadLocals to store buffers and arrays and not have to reallocate them on every page hit.
Also would like to get rid of the synchronized block in the DotResourceLoader that we have seen act up.
- Retain full backward compatibility
- Ensure all tests pass
- Benchmark the code before and after
dotCMS Version
latest