[gatein-issues] [JBoss JIRA] Commented: (GTNPORTAL-506) Performance tuning of navigation portlet

[Marek Posolda (JIRA)]

    [ https://jira.jboss.org/jira/browse/GTNPORTAL-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12518678#action_12518678 ] 

Marek Posolda commented on GTNPORTAL-506:
-----------------------------------------

I tried to run test against portal with 5 nodes (including portalNavigation, groupNavigation, register, Home and one my test page) and 9 nodes (4 additional nodes which I created). I saw only small degradation (around 3% ) between these two builds. Main difference I saw is in UIUserToolbarSitePortlet.getCurrentPortalnavigation which calls PageNavigationUtils.filter
and then method PageNavigationUtils.filterNodeNavigation is called once for each navigation node. But I believe that 3% is acceptable.

> Performance tuning of navigation portlet
> ----------------------------------------
>
>                 Key: GTNPORTAL-506
>                 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-506
>             Project: GateIn Portal
>          Issue Type: Task
>          Components: Performance
>    Affects Versions: 3.0.0-Beta04
>         Environment: Ubuntu linux,
> Sun JDK 1.6,
> EAP5 with GateIn from trunk (revision 1165) deployed
>            Reporter: Marek Posolda
>            Assignee: Julien Viet
>             Fix For: 3.0.0-GA
>
>
> There is small performance degradation for each visible page on navigation portlet (navigation bar). Since method getPage from UserPortalConfigService is called for each visible page on navigation bar and it costs some time even if pages are cached. so rendering of UINavigationPortlet costs more time.
> Degradation is not big. When the request is sent to page on portal with only 2 visible pages on navigation bar, then maximum throughput was 527.8 requests/s. If there are 6 visible pages on navigation bar, then maximum throghput is 491.9 requests/s. So small difference but it's here.
> Performance degradation is not here, when pages are configured to be non-visible in portal.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira