Hi ,
there is a bunch of pages parent and with child pages that need to move to another space , when we move these pages or change permission pages content indexing queue happening and it crushed the pages because of high CPU usage
I am moving that issue temporarily with this method
My question is for a permanent solution
Q1: What is recommended CPU and MEM for content indexing queue finishing faster?
Q2: Is there any limit or reduce that queue with child pages? I mean what is recommended pages that how many child pages need to be 1 parent page for better working content indexing ?
Thanks for your support in advance
Hello @Support Eigen
Welcome to the Atlassian Community!!
This is very vast topic of discussion. I can see you are using confluence server. The recommended hardware requirements can be found at the following URL: https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html
To troubleshoot the confluence indexing, these are the some important points as mentioned in the documentation: https://confluence.atlassian.com/confkb/confluence-indexing-troubleshooting-guide-1035242274.html
Now, the answer of your questions.
A1: Need to the server configuration and application configuration settings on the server. You can follow some of the documentation or might be required to follow more documentation depends upon the identifying the issue.
https://confluence.atlassian.com/doc/content-index-administration-148844.html
https://confluence.atlassian.com/doc/configuring-system-properties-168002854.html
https://confluence.atlassian.com/doc/recognized-system-properties-190430.html
A2: There is such limit in child page.
the maximum size of the confluence is recommended to 100,000 characters.
https://jira.atlassian.com/browse/CONFSERVER-12773
https://confluence.atlassian.com/confkb/slow-page-rendering-of-large-pages-due-to-http-post-limitations-183137.html
Let me know in case of any further help.
Thanks,
Prashant Sultania
Note: Upvote, Like or Accept Answer if it resolves your query
Hi Prashant,
Thanks for the comprehensive reply , I will try these guides and update about solution
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You mention CPU and memory here, which are important, but the indexing is also heavy on the disk. If you've got a slow read/write on your local disk where the index is stored, no amount of CPU or memory is going to help.
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.