nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Recommended Confluence hardware resources for around 15k attachments

Demo User

Hi all,

I just read the webpage regarding server hardware recommendations for Confluence but would be interested in some more insights. WerRe thinking about using Confluence for storing big amounts of documents (mostly doc and pdf). We currently estimate:

- Up to 2.000 users

- Around a 100 spaces

- Up to 2.500 pages long term

- Around 20.000 file attachments, mostly doc and pdf

Do you have a hardware recommendation for this? Is the amount of attachments even reasonable? Any experiences to what extend this amount of docs might harm indexing and search?

I'm thanksful for your insights!

Regards, Rene

Best Regards, René

Accepted answers

All comments

AnnWorley

The page you refer to has an Example site with 207,659 attachment files, taking up 105 GB of disk space. That is encouraging as far as the feasibility is concerned. You will want to make sure you have sufficient disk space as the attachments are stored on the file system.

It would be a good idea to set up a test environment first, to fine tune your hardware before putting it into Production.

The indexing is something else you will want to test in your staging environment. I hope to hear from other members of the Community with regard to indexing large numbers of attachments.

Hermance NDounga

Hey,

I found this documentation which shows different use cases for hardware requirements. I'm not a specialized in Confluence installation, but I think that the global size of the attachment is more important than the number.

Beside this, if I can give you an advice, to take full advantage of Confluence, your documents should be Confluence pages themselves -- continually accessible via the browser, while supporting various forms of rich content, dynamic reports, tables etc. Confluence even allows you to import existing Word and .text documents to Confluence wiki pages.

So I think that converting some of your attachements in Confluence pages would be better - no only in terms of performance.

Aron Gombas _Midori_

I can't recommend a precise HW setup for this, but I can confidently say that we have seen Confluence instances that are 1-2 magnitude larger than what you are targeting!

So, Confluence will be able to scale to these metrics, that is sure.

Demo User

Hi,

thanks for your reply. I also read the documentation you mentioned, unfortunately it does not list CPU or RAM requirements for the installation with the thousands of attachments. However, knowing Confluence can basically deal with these large amounts of attachments is still good to know!

Regards, René

Demo User

Hi Aron,

thanks, that's good to hear. Do you know anything about the HW setup for the instances you mentioned?

Regards, René

Demo User

Hi Ann,

thanks for your answer. A test environment would surely make sense. Is there any built in functionality or best practice to test uploading/indexing large amounts of data? If not, my approach would be some script using the REST API to create pages and upload attachments.

Regards, René

Aron Gombas _Midori_

Unfortunately, no.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

hardware