You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/07/31 16:32:05 UTC

[jira] [Commented] (TAP5-2337) Reduce number of calls of AbstractStringBuilder.expandCapacity

    [ https://issues.apache.org/jira/browse/TAP5-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649287#comment-14649287 ] 

Jochen Kemnade commented on TAP5-2337:
--------------------------------------

I recently committed some changes in that area ({{f13311782acc8b8a3da311623761cb970d04387e}}, {{ef7060efadfec0652aa7758a3376e190d13737aa}}, and {{c409f589b235ba58fc61007b080dd39b4e53be39}}. They should have improved the situation in {{org.apache.tapestry5.dom.Element.toMarkup(Document, PrintWriter, Map<String, String>)}}. Maybe this is not so much of an issue anymore.

> Reduce number of calls of AbstractStringBuilder.expandCapacity
> --------------------------------------------------------------
>
>                 Key: TAP5-2337
>                 URL: https://issues.apache.org/jira/browse/TAP5-2337
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: Michael Mikhulya
>            Priority: Minor
>              Labels: patch, performance
>         Attachments: 0001-TAP5-2337-Reduce-number-of-calls-of-AbstractStringBu-jk.patch, 0001-TAP5-2337-Reduce-number-of-calls-of-AbstractStringBu.patch, Tapestry-StringBuilder.png
>
>
> During profiling of Tapestry framework I found that AbstractStringBuilder.expandCapacity is called very frequently.
> There is a patch that get rid of creation StringBuilder with following calls of expandCapacity (which allocate memory and copy current content into it).
> I have to thank Dmitriy Ilyin, who helped me to investigate the issue and to find the simplest solution (actually we get a little bit less code while improving performance).
> With this improvement time per request decreased on 0.5ms (1% of overall time)on our test. All measurements were done with apache benchmark after warm up phase.



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