[
https://issues.apache.org/jira/browse/WICKET-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476108
]
Johan Compagner commented on WICKET-201:
----------------------------------------
for 1.3 the SecondLevelCache and its FilePageStore is pretty much done.
The performance lose we have for the serialization and saving (2 separate
threads) are around 15% under very heavy load. (App1Test1) compared to
HttpSessionStore.
Thats in my eyes very acceptable. And under normal load you won't even notice
it because the serializing thread can handle it fine.
The only thing we could do now is move the soft cache we have now in the Store
it self through the FilePageStore and soft cache the byte[] so that those don't
have to be loaded from disk.
But maybe we can do both. If a history entry in the browser is a new page in
wicket then the current soft cache does it works.
But if it is a version of the current page. the soft cache doesn't do anything
anymore (because there is no undo information anymore in a page)
Also maybe the FilePageStore should be abstracted then. So that the
serialization is done by a common base class. And the actual saving can be done
to anything you want.
(and then port it all to 2.0!)
> refactor storing pages and versions
> -----------------------------------
>
> Key: WICKET-201
> URL: https://issues.apache.org/jira/browse/WICKET-201
> Project: Wicket
> Issue Type: Bug
> Reporter: Eelco Hillenius
> Assigned To: Johan Compagner
> Priority: Critical
> Fix For: 1.3, 2.0
>
>
> See http://www.nabble.com/refactor-storing-pages-and-versions-tf2943670.html
> for a discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
