[
https://issues.apache.org/jira/browse/WICKET-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099322#comment-17099322
]
ASF subversion and git services commented on WICKET-6778:
---------------------------------------------------------
Commit b092021b436e2ea842d61e17746b4f51449124c9 in wicket's branch
refs/heads/wicket-6778 from Emond Papegaaij
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=b092021 ]
WICKET-6778: put REMOVALS_KEY metadata behind a flag
> Clearing MarkupContainer.REMOVALS_KEY is expensive
> --------------------------------------------------
>
> Key: WICKET-6778
> URL: https://issues.apache.org/jira/browse/WICKET-6778
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 9.0.0-M5
> Reporter: Emond Papegaaij
> Priority: Major
>
> The {{REMOVALS_KEY}} metadata on {{MarkupContainer}} is cleared on every
> request. This is an expensive operation and often unnecessary. By putting
> this operation behind a request flag, it can often be avoided.
> An alternative approach is to check if the key is set (via
> {{getMetaData(REMOVALS_KEY)}}) and only clear it when it's set. This is
> faster than current master, but slower than using a flag.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
