Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WICKET-6771 Performance issues with component metadata #420

Closed
wants to merge 6 commits into from

Conversation

theigl
Copy link
Contributor

@theigl theigl commented Apr 27, 2020

This PR provides a JMH benchmark that demonstrated performance issues with accessing component metadata.

The benchmark is executed by running the main method in ComponentBenchmarks. It should be run 2-3 times to get reliable results.

On my machine the results are:

Run complete. Total time: 00:02:44

Benchmark Mode Cnt Score Error Units
ComponentBenchmarks.detachComponentWithFlags thrpt 20 12295,363 ± 71,343 ops/s
ComponentBenchmarks.detachComponentWithMetaData thrpt 20 8855,321 ± 34,743 ops/s

I couldn't get to the root cause of the performance issues but the PR suggests a possible workaround: Using request-level flags that are checked before accessing component metadata.

https://issues.apache.org/jira/browse/WICKET-6771

@theigl theigl force-pushed the WICKET-6771-metadata-performance branch 2 times, most recently from 02a91f1 to 6b885e2 Compare April 29, 2020 09:20
@theigl theigl force-pushed the WICKET-6771-metadata-performance branch from 6b885e2 to 0547466 Compare April 29, 2020 09:49
…a-performance

# Conflicts:
#	wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java
@theigl theigl closed this Apr 29, 2020
@theigl theigl deleted the WICKET-6771-metadata-performance branch September 13, 2020 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant