[
https://issues.apache.org/jira/browse/WICKET-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Teppo Kurki updated WICKET-1763:
--------------------------------
Attachment: InjectionFlagCachingGuiceComponentInjector.java
One solution: cache the to-inject-or-not information per class. Resulted in
30-40% decrease in request serving time in my test application with some
hundreds of rows and about 10 components per row.
> Cache the injection flag per class to improve performance
> ---------------------------------------------------------
>
> Key: WICKET-1763
> URL: https://issues.apache.org/jira/browse/WICKET-1763
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-guice
> Affects Versions: 1.3.3, 1.3.4
> Reporter: Teppo Kurki
> Attachments: InjectionFlagCachingGuiceComponentInjector.java
>
>
> Finding the guice annotations for each object instantiation is a rather
> heavyweight operation. This causes considerable overhead with large lists
> that have complicated component structure per row, which is totally
> unnecessary for stock wicket components that do not contain any Guice
> annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
