[
https://issues.apache.org/jira/browse/JS2-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Sean Taylor resolved JS2-739.
-----------------------------------
Resolution: Fixed
The decorator cache is in place. Contribution from myself and Woonsan Ko, a
little pair programming across the Pacific ;)
It is disabled by default, as I believe the performance gains are not
worthwhile until you get into heavy loads
It now supports both JetspeedCache and session caching
My opinion is that the entire Decoration code, and especially Content* classes,
should be greatly improved on in the next release (2.2.)
> Improve Algorithms for Resource Validation and Template Localization
> --------------------------------------------------------------------
>
> Key: JS2-739
> URL: https://issues.apache.org/jira/browse/JS2-739
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Decorations/Themes
> Affects Versions: 2.1.1
> Reporter: David Sean Taylor
> Assignee: David Sean Taylor
> Fix For: 2.1.1
>
>
> During load testing, we discovered the Decoration valve was calling code in
> the BaseDecorator that inefficiently made calls to validate resources,
> combined with applying a seldom used mediatype/language/countrycode fallback
> algorithm. This effort will optimize these inefficiencies with caching and
> optionalizing the fallback algorithm and resource validation. The overall
> expense of the existing algorithm was leading to as much as 18-24% CPU usage
> per request. Additionally, there are other calls made to locating templates
> like from velocity templates, where we may gain some more performance
> improvement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
