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

ASF GitHub Bot commented on WICKET-7047:
----------------------------------------

theigl commented on code in PR #579:
URL: https://github.com/apache/wicket/pull/579#discussion_r1168181660


##########
wicket-util/src/main/java/org/apache/wicket/util/string/Strings.java:
##########
@@ -1089,7 +1089,7 @@ public static CharSequence toMultilineMarkup(final 
CharSequence s)
                        return null;
                }
 
-               final AppendingStringBuffer buffer = new 
AppendingStringBuffer();
+               final AppendingStringBuffer buffer = new 
AppendingStringBuffer((int) (s.length() * 1.1));

Review Comment:
   We have the exact same logic in `Strings.escapeMarkup`:
   
   
https://github.com/apache/wicket/blob/d51883862a448e26f8d973a24756ea7e03259de7/wicket-util/src/main/java/org/apache/wicket/util/string/Strings.java#L305
   
   A constant would have to be something like 
`ESTIMATED_OVERHEAD_OF_MULTILINE_MARKUP`. I think a comment would be better.





> Improve initial buffer capacity for Strings.toMultilineMarkup
> -------------------------------------------------------------
>
>                 Key: WICKET-7047
>                 URL: https://issues.apache.org/jira/browse/WICKET-7047
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-core
>    Affects Versions: 9.12.0
>            Reporter: Thomas Heigl
>            Assignee: Thomas Heigl
>            Priority: Major
>
> We currently create an AppendingStringBuffer with default capacity of 16 in 
> Strings#toMultilineMarkup. Since we know the size of the original string and 
> can take a guess at the additional length required for markup, it makes sense 
> to size this buffer appropriately.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to