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

["Tomek Rękawek (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomek Rękawek resolved SLING-4544.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Engine 2.4.4

Commited in r1707283.

> 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
>            Assignee: Tomek Rękawek
>              Labels: performance
>             Fix For: Engine 2.4.4
>
>         Attachments: SLING-4544.patch, Screen Shot 2015-03-25 at 10.42.05.png
>
>
> I am profiling an application where 1-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)