Hello,
We have faced an issue and some complains from customers about slow loading of large page trees. For example, in the following space: https://docs.onapp.com/display/APIM/OnApp+6.0+API+Guide
We also use Scroll Viewport and Scroll Versions add-ons. Here is the link to the same space via Scroll Viewport: https://docs.onapp.com/apim/latest
We've already contacted Scroll Viewport support about the same issue and received the next response:
"If it takes longer than in Confluence to generate the page tree, then I would recommend asking this question in the Viewport Google Group where our developers can suggest something outside of the product documentation. There is no other solution I can think of apart from what’s already in the documentation (https://help.k15t.com/scroll-viewport/latest/output-a-page-tree-137860108.html)."
We've compared the time of loading in Confluence and Viewport and came to the conclusion that the time is the same. So it takes too long to generate the page tree both in Confluence and Viewport.
As for the Viewport, we use the Lazy-loading trees but it doesn't help to load the tree faster than in Confluence.
Could you please provide any suggestions on how to load page tree faster? Are there any solutions to the issue?
Thanks and have a nice day.
Kateryna,
We are aware of an issue where page trees are taking a long time to load in large Confluence spaces:
Exactly how large is your space, and how long does the page tree take to load? You can test by creating a HAR file and seeing what is taking especially long to load, but it's highly likely it's the issue above.
If that's the case, you might need to break up the space into smaller spaces in order to increase the load time.
I also wanted to let you know that your Confluence version of 6.1.2 will be reaching End of Life in March, so you may want to consider upgrading soon. Upgrading insures that you have the latest bug fixes and security releases, so it is beneficial to do so.
Regards,
Shannon
@Shannon S I also facing this issue in 6.13.3 , any workaround will be appreciated this is critical bug, i wounder why no workaround at-least.
Best regards,
Mo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mo,
I would recommend having a look at @Tobias Anstett _K15t_'s response below and see if that helps you.
Otherwise, you'll want to test using the HAR file as mentioned, and breaking down your space into smaller spaces will help.
Let me know if you have any questions about that.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Shannon S After Upgrade to latest confluence version 6.15.8, issue was resolved.
Best regards,
Moses
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Moses,
Thank you for confirming that! Glad to hear you were able to resolve with the latest update.
Take care, and have a pleasant rest of your week.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Shannon S I am very happy now we can upgrade our production server :)
Have a pleasant weekend too
Best regards,
Mo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When working in large versioned spaces containing many pages, you might notice small performance decreases affecting the page tree's rendering time.
There are a number of ways you can tune Confluence's cache to help solve this issue.
Please refer to the following article for details. This will most likely fix your issues.
Best, Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.