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

Posted to commits@wicket.apache.org by "Matej Knopp (JIRA)" <ji...@apache.org> on 2007/11/01 09:34:51 UTC

[jira] Resolved: (WICKET-792) Calls to getString() are sloooooow.

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

Matej Knopp resolved WICKET-792.
--------------------------------

    Resolution: Invalid

I believe this is not valid, as we cache the strings. If I'm wrong and the caching doesn't work as expected, please re-open.

> Calls to getString() are sloooooow.
> -----------------------------------
>
>                 Key: WICKET-792
>                 URL: https://issues.apache.org/jira/browse/WICKET-792
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.0-beta2
>            Reporter: Alastair Maw
>            Assignee: Matej Knopp
>             Fix For: 1.3.0-beta5
>
>         Attachments: cpu-hotspots.png
>
>
> getString() is currently very very inefficient. It's particularly inefficient if you use it inside a ListView calling the same thing multiple times.
> See the attached profiler screendump.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.