Why should you avoid swapping on the Confluence server?

Why should you avoid swapping on the Confluence server?

• A. Swapping has no effect on performance
• B. Swapping reduces RAM usage
• C. Swapping does not affect garbage collection
• D. Swapping can lead to a fatal cluster error

Answer: (D)

Swapping is something you want to avoid on a Confluence server because it turns RAM into slower disk space, which causes unpredictable and lengthy pauses for the Java process. When the OS starts paging memory, the application can experience long GC pauses and latency spikes as it has to fetch swapped pages back into memory. In a clustered Confluence environment, these delays can cause nodes to miss heartbeats or become out of sync with the cluster, potentially triggering a fatal cluster error. Keeping memory pages in RAM ensures stable performance, predictable garbage collection, and healthier cluster behavior.

Swapping is something you want to avoid on a Confluence server because it turns RAM into slower disk space, which causes unpredictable and lengthy pauses for the Java process. When the OS starts paging memory, the application can experience long GC pauses and latency spikes as it has to fetch swapped pages back into memory. In a clustered Confluence environment, these delays can cause nodes to miss heartbeats or become out of sync with the cluster, potentially triggering a fatal cluster error. Keeping memory pages in RAM ensures stable performance, predictable garbage collection, and healthier cluster behavior.