[SLING-4240] Improve Sightly engine performance

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Scripting Sightly Engine 1.0.0
• Component/s: Scripting
• Assignee: Felix Meschberger
• Reporter: Radu Cotescu
• Created: 13/Dec/14 11:28
• Updated: 30/Mar/15 12:19
• Resolved: 15/Dec/14 13:27

Description

Several areas of the engine's implementation can be improved to greatly reduce compilation & rendering times:

• rely on the dynamic classloader's cache rather than compile Use-API POJOs all the time
• reduce the number of repository reads in favour of events for deducing if a Sightly script or Use-API POJO needs to be recompiled
• use a per thread admin resource resolver instead of creating many resolvers in various components during the lifecycle of a request
• optimise the RenderContext implementation code that handles object methods and fields detection

Issue Links

• is related to: SLING-4093 run performance tests to compare with JSP and Sightly
• is related to: SLING-4493 Sightly: Create performance tests