What are the minimum heap size requirements for Confluence and Synchrony?

What are the minimum heap size requirements for Confluence and Synchrony?

• A. 512 MB for Confluence and 1 GB for Synchrony
• B. 1 GB for Confluence and 1 GB for Synchrony
• C. 2 GB for Confluence and 2 GB for Synchrony
• D. 256 MB for Confluence and 256 MB for Synchrony

Answer: (D)

Understanding memory needs for these Atlassian components begins with the concept of the Java heap—the space the JVM uses to store objects during runtime. The smallest amount of heap that allows Confluence and Synchrony to start and operate, even in a minimal setup, is 256 MB for each component. This 256 MB baseline gives the JVM enough room to initialize and run basic tasks without immediately running into memory errors. It’s the minimum, not a recommended production target. In real deployments you’ll want to allocate more memory to handle indexing, user activity, and real-time collaboration, so expect production setups to use significantly more than this. If you try to go smaller than 256 MB, startup or runtime failures are likely. The same minimum applies to Synchrony, though how you deploy (shared or separate processes) can influence overall memory planning.

Understanding memory needs for these Atlassian components begins with the concept of the Java heap—the space the JVM uses to store objects during runtime. The smallest amount of heap that allows Confluence and Synchrony to start and operate, even in a minimal setup, is 256 MB for each component. This 256 MB baseline gives the JVM enough room to initialize and run basic tasks without immediately running into memory errors. It’s the minimum, not a recommended production target. In real deployments you’ll want to allocate more memory to handle indexing, user activity, and real-time collaboration, so expect production setups to use significantly more than this. If you try to go smaller than 256 MB, startup or runtime failures are likely. The same minimum applies to Synchrony, though how you deploy (shared or separate processes) can influence overall memory planning.