[GROOVY-9716] Close Performance Gap in Groovy Templates

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Templating
• Assignee: Unassigned
• Reporter: Suminda Dharmasena
• Created: 03/Sep/20 16:44
• Updated: 16/Feb/21 04:27

Description

Groovy Templates seams to be comparatively less performant than other templating solutions. E.g.: https://github.com/jreijn/spring-comparing-template-engines

 

Can this performance gap be closed making it the most performant?

 

Also is it possible to add partials evaluation support when only parts of the template need reevaluation when part of the data changes.

 

Possible areas to improve:

• Faster reflection can be used like used in: https://github.com/EsotericSoftware/reflectasm
• Be lock-free as much as possible. Maybe disruptor-proxy pattern can be used but with Conversant Disruptor limited to the methods which need synchronising
• Use faster primitive collections
• Use faster logger like Log4J2 with Conversant Disruptor

NB: This benchmark may be dated but some outperform stringbuilder: https://github.com/greenlaw110/template-engine-benchmarks