Scroll documentation theme page tree performance

Follow

Ernst Stefan (ERS)

October 01, 2015 09:53

Hi,

we have a Scroll Versions space with around 9000 pages. The page tree on the left is relatively slow and renders only after a few seconds wait time. Is there any way to optimize it or to cache it?

 

thanks in advance

0

• 

  Nils Bier October 06, 2015 11:24

  Hi Stefan,

  thanks for contacting us. There are a few tweaks regarding the caching values, see https://confluence.atlassian.com/doc/cache-statistics-150472.html.

  Furthermore the performance depends on the structure of your space (e.g. if there are hundreds of pages on the same level, the page tree gets slower). Currently the roles are set on every versioned page, which can lead to performance issues depending on your Confluence system and the space structure.

  In Scroll Versions 3.0 (planned to be released within the next 8 weeks), we'll further improve the performance if you're using a private master space approach, as the Scroll Versions roles will not be mandatory anymore and the "normal" Confluence space permissions can be used.

  I hope that information help.

  Best,Nils

  0

  Comment actions Permalink
• 

  Matt Reiner November 03, 2016 14:35

  Nils, which cache value(s) should be adjusted to improve the page tree speeds?

  0

  Comment actions Permalink
• 

  Nils Bier November 11, 2016 10:33

  Hi Matt,

  Thanks for asking.
  You can find further information about cache performance tuning in the Atlassian Documentation: https://confluence.atlassian.com/doc/cache-performance-tuning-169119133.html

  The following information from this page is relevant when it comes to the page tree speed:
  
  - Content Objects cache (com.atlassian.confluence.core.ContentEntityObject)
  should be set to at least 20-30% of the number of content entity objects (pages, comments, emails, news items) in your system. To find the number of content entity objects, use the query select count(*) from CONTENT where prevver is null.
  - Content Body Mappings cache (com.atlassian.confluence.core.ContentEntityObject.bodyContents)
  should be set to at least 20% of the number of content entity objects (pages, comments, emails, news items) in your system. To find the number of content entity objects, use the query select count(*) from CONTENT where prevver is null.
  - Space permissions by ID cache (com.atlassian.confluence.security.SpacePermission)
  should be set to the number of space permissions in your deployment (a good rule of thumb is 20 times the number of spaces). You can find the number of space permissions using the query select count(*) from SPACEPERMISSIONS.

  Besides that, please also have a closer look at the following entries and try to optimize your stats (with the information from the section "Cache tuning example"):
  
  - Content Properties / Object Properties
  - Content Permissions
  - Content Permission Sets
  - Page Children / Page Ancestors

  The effectiveness for all those entries is important. If you see problems here, please feel free to play around with the cache settings here.

  I hope that input helps. Please let me know if you have any further questions.

  Cheers,
  Nils

  0

  Comment actions Permalink

Please sign in to leave a comment.