Uploaded image for project: 'XWiki Platform'
  1. XWiki Platform
  2. XWIKI-8801

DefaultVelocityManager's getVelocityEngine() method seems to be taking too long to execute

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.4-rc-1
    • Fix Version/s: 5.0-milestone-1
    • Component/s: Old Core
    • Labels:
      None
    • Difficulty:
      Unknown
    • Documentation:
      N/A
    • Documentation in Release Notes:
      N/A
    • Similar issues:

      Description

      According to Ludovic on mailing list (see http://markmail.org/thread/na33ve23kvgjjlul):

      Velocity is clearly quite expensive. Now I see particularly:

      8.5% - com.xpn.xwiki.render.DefaultVelocityManager.getVelocityEngine

      Would this mean we are spending 8,5% of the time getting the velocity
      engine to use ?
      This sounds a lot.

      One reason I could see is that this method is synchronized and thus when there are lots of threads, they'll wait to get the lock on the object.

        Attachments

          Activity

            People

            • Assignee:
              vmassol Vincent Massol
              Reporter:
              vmassol Vincent Massol
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: