[
https://issues.apache.org/jira/browse/WICKET-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486064#comment-17486064
]
ASF subversion and git services commented on WICKET-6952:
---------------------------------------------------------
Commit 76a47ab37d30e3548bd3bb86d02657a28d0cc077 in wicket's branch
refs/heads/wicket-9.x from Thomas Heigl
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=76a47ab ]
WICKET-6952 Performance improvements for `Strings.isEmpty()` (#497)
(cherry picked from commit f95cbf4b072ee87a4ceb7cb61a2c79d82744b7bc)
> Performance improvements for Strings.isEmpty
> --------------------------------------------
>
> Key: WICKET-6952
> URL: https://issues.apache.org/jira/browse/WICKET-6952
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 9.7.0
> Reporter: Thomas Heigl
> Assignee: Thomas Heigl
> Priority: Minor
>
> {{Strings.isEmpty}} is one of the most called methods in our application and
> consistently shows up as hot in our production profiler.
> Two simple performance optimizations can be tried:
> - Overload the method with a {{String}} parameter, to help the JIT compiler
> with it's decision to inline the method
> - Avoid calling {{String.trim}} if the first character isn't whitespace
> See https://github.com/apache/wicket/pull/497.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
