Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-31525

Children display macro with include excerpt gives performance issue

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      When a page has a "Children display" macro with the option "include excerpt" checked, it gives a performance issue. When opening that page it will take about 30 seconds to load the page and the cpu will take a high load for that time.

      When unchecking the "include excerpt" option the page will load normally.

      Cheers,
      Herman Wander

            [CONFSERVER-31525] Children display macro with include excerpt gives performance issue

            Significant problem - is there a way that an admin can limit the number of child items that will load on a page.  we are running 7.13.3 and need to patch for this

            Sandi Ameen added a comment - Significant problem - is there a way that an admin can limit the number of child items that will load on a page.  we are running 7.13.3 and need to patch for this

            Andrews added a comment -

            This load impact our system performance. 

            Still occurring on the Confluence 6.15.2 any fix for this?

            Andrews added a comment - This load impact our system performance.  Still occurring on the Confluence 6.15.2 any fix for this?

            Hey,

             

            This load impact our system performance. Why there is no responsible person for this issue since 2013 ??

            Still occuring on the Confluence 6.13.2

             

            Regards,

            Antoine

            Antoine Ferron added a comment - Hey,   This load impact our system performance. Why there is no responsible person for this issue since 2013 ?? Still occuring on the Confluence 6.13.2   Regards, Antoine

            GerardYin added a comment -

            Generally, the children display macro is poorly optimized.

            1. It does not load asynchronously, so the whole page including this macro is slow to display
            2. On my Confluence 6.6 instance, a page with a children include (500 children page displayed) takes between 4 and 10 seconds to load. I'm not even displaying excerpts.

            GerardYin added a comment - Generally, the children display macro is poorly optimized. It does not load asynchronously, so the whole page including this macro is slow to display On my Confluence 6.6 instance, a page with a children include (500 children page displayed) takes between 4 and 10 seconds to load. I'm not even displaying excerpts.

            sinan.yildirim247208441 added a comment - - edited

            In our case, customers have a parent page with more than 700 child pages. And the parent page use childrendisplay macro.

            Loading the page with enabled excerpt takes more than 7 minutes. This load impact our system performance. Why there is no responsible person for this issue since 2013 ??

            sinan.yildirim247208441 added a comment - - edited In our case, customers have a parent page with more than 700 child pages. And the parent page use childrendisplay macro. Loading the page with enabled excerpt takes more than 7 minutes. This load impact our system performance. Why there is no responsible person for this issue since 2013 ??

            I will try this. Thanks!

            sniadek sniadek added a comment - I will try this. Thanks!

            Chad Barnes added a comment - - edited

            Time marches on and there isn't much to the configuration now. We are currently running:

            Confluence 5.6.3
            Java 1.7 (u71)
            Args: -XX:+UseG1GC -Xms4096m -Xmx6144m -XX:-UseGCOverheadLimit -XX:MaxPermSize=384m

            We are several weeks into using G1 for Confluence garbage collection... and it has been solid. No noticeable performance difference and the hands-off approach to GC tuning is much appreciated.

            You'll also get a lot of improvement by optimizing your caches. You have to do this for your own unique utilization, but it is well worth it. Optimizing caches took our dashboard load time from >10s to <5s.

            https://confluence.atlassian.com/display/DOC/Cache+Performance+Tuning
            http://www.adaptavist.com/w/confluence-cache-effectiveness/

            Chad Barnes added a comment - - edited Time marches on and there isn't much to the configuration now. We are currently running: Confluence 5.6.3 Java 1.7 (u71) Args: -XX:+UseG1GC -Xms4096m -Xmx6144m -XX:-UseGCOverheadLimit -XX:MaxPermSize=384m We are several weeks into using G1 for Confluence garbage collection... and it has been solid. No noticeable performance difference and the hands-off approach to GC tuning is much appreciated. You'll also get a lot of improvement by optimizing your caches. You have to do this for your own unique utilization, but it is well worth it. Optimizing caches took our dashboard load time from >10s to <5s. https://confluence.atlassian.com/display/DOC/Cache+Performance+Tuning http://www.adaptavist.com/w/confluence-cache-effectiveness/

            Chad, can you attach your configuration file? I have the same issue and it is very painful.
            Thanks!

            sniadek sniadek added a comment - Chad, can you attach your configuration file? I have the same issue and it is very painful. Thanks!

            This is still an issue. However, the slow performance was exaggerated in our instance by pre 1.7 java optimizations that carried over into our upgrade (which included Java 1.7). We basically removed all of the JVM optimization suggestions (that we got from Atlassian documentation) and performance improved a lot. Children display is still slow, but not in the 30 second range.

            If you have very poor performance... try stripping away all of your java arguments except the Xmx and Xms settings. Let the JVM do the rest.

            Chad Barnes added a comment - This is still an issue. However, the slow performance was exaggerated in our instance by pre 1.7 java optimizations that carried over into our upgrade (which included Java 1.7). We basically removed all of the JVM optimization suggestions (that we got from Atlassian documentation) and performance improved a lot. Children display is still slow, but not in the 30 second range. If you have very poor performance... try stripping away all of your java arguments except the Xmx and Xms settings. Let the JVM do the rest.

            I know ticket is still open but Chad did you guys do any performance tuning that helped with the issue? Also for the Atlassian any updates on this?

            Cesar Aguilar added a comment - I know ticket is still open but Chad did you guys do any performance tuning that helped with the issue? Also for the Atlassian any updates on this?

              Unassigned Unassigned
              8ffb8efb92e9 Herman Wander
              Affected customers:
              34 This affects my team
              Watchers:
              39 Start watching this issue

                Created:
                Updated: