Confluence 2.5 has reached end of life
Check out the [latest version] of the documentation
Confluence provides stastical information about its internal caches that allows you to track the size and hit ratio of each cache and tune it if necessary, for better performance. See Performance Tuning for more information.
To view the cache statistics, go to the 'Administration Console' and click on 'Cache Statistics' in the left panel. Here, you will find a list of all object cached within Confluence. For example, one of the main one is the ContentEntityObject
com.atlassian.confluence.core.ContentEntityObject (Alive): flush
_____________________ACCESSES__________________
Size |
Total |
Hits |
Not Found |
Expired |
Ratio |
|---|---|---|---|---|---|
5000 |
24827480 |
11332536 |
13494944 |
0 |
45% |
About the generated numbers :
Size: |
the max number of items in the cache (can be configured in |
|---|---|
Accesses, Total: |
the number of reads from the cache |
Accesses, Hits: |
the number of reads accessing cache and required content existed |
Accesses, Not Found: |
the number of reads accessing cache and required content was not-found |
Accesses, Expired: |
the number of items which were evicted from the cache, due to age or replacement by new entries ( |
Ratio: |
the percentage of reads which were hits |
For instance to calculate Ratio :
Hits/Total x 100 = Ratio 11332536/24827480 = 0.45645131 x 100 = 45%
and to calculate Total :
Total = Hits + Not Found + Expired 24827480 = 11332536 + 13494944 + 0
flush - clears cache
The upcoming new release of cluster-able Confluence 2.3 will be using distributed cache called Tangosol Coherence.
Performance Tuning
If you require to tune your application when under high usage, you may like to review this document for suggestions.


