You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Joel Richard (JIRA)" <ji...@apache.org> on 2015/03/25 10:42:54 UTC

[jira] [Created] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

Joel Richard created SLING-4544:
-----------------------------------

             Summary: Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker
                 Key: SLING-4544
                 URL: https://issues.apache.org/jira/browse/SLING-4544
             Project: Sling
          Issue Type: Improvement
          Components: Engine
    Affects Versions: Engine 2.4.0
            Reporter: Joel Richard


I am profiling an application where up to 5% of the rendering time is spent in MessageFormat.format for SlingRequestProgressTracker.log (see attached screenshot). Since the advanced capabilities of MessageFormat are not required here, it should be rather easy to implement a utility which supports {x} as well but is much faster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)