Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.2-milestone-1
-
Unknown
-
N/A
-
N/A
-
Description
Each time the current velocity engine is asked to the VelocityManager it spend ages just to calculate a cache key used to access the actual velocity engine.
The reason it's slow is that at each call velocity manager is trying to find the location of macros.vm template and this is very slow.
Attachments
Issue Links
- is related to
-
XWIKI-11187 The skin is unstable on first run after upgrade from 5.4.5 to a 6.2(.x)
- Closed
-
XWIKI-11026 During exports, "macros.vm" from "defaultbaseskin" is always used instead of the one from the current skin
- Closed
- relates to
-
XWIKI-11213 The new velocity engine cache key cache is not safe enough
- Closed