[
https://issues.apache.org/jira/browse/WICKET-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117564#comment-17117564
]
Thomas Heigl commented on WICKET-6774:
--------------------------------------
[~papegaaij]: I attached a new benchmark that renders the components. Again,
your branch is as fast as master and in some cases minimally faster. But the
difference is so small that I'm not sure they are statistically significant.
The biggest surprise for me in all of these benchmarks is how much overhead
ajax behaviors have:
{code:java}
ComponentBenchmarks.renderComponent thrpt 7
4851,889 ± 504,131 ops/s
ComponentBenchmarks.renderComponentWithBehavior thrpt 7
4286,133 ± 368,456 ops/s
ComponentBenchmarks.renderComponentWithAjaxBehavior thrpt 7
1266,673 ± 136,133 ops/s{code}
This might be something worth profiling to see if there is any room for
improvement.
> Separate model, behaviors and metadata into separate fields
> -----------------------------------------------------------
>
> Key: WICKET-6774
> URL: https://issues.apache.org/jira/browse/WICKET-6774
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 9.0.0-M5
> Reporter: Thomas Heigl
> Priority: Minor
> Attachments: ComponentBenchmarks.java, ComponentBenchmarks.java,
> benchmarks.png
>
>
> While investigating performance issues with metadata in WICKET-6771, I
> discovered that significant performance gains can be achieved by separating
> models, behaviors, and metadata into separate fields.
> Currently, all three types of data are stored in a single, untyped field
> {{Component.data}}. The idea is to minimize memory overhead by creating as
> few objects as possible.
> If a model or a single behavior or metadata is added, {{data}} stores only a
> reference to the object. When additional data is added, the reference becomes
> an array.
> This is the most memory-efficient way to store these three types of data. But
> it comes with a cost: code to manipulate that data structure is complex and
> not as efficient because it has to take all possible combinations of data
> into account.
> I suggest introducing 3 separate fields for the 3 types of data, trading a
> little bit of memory for reduced complexity and performance gains.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
