If you are having performance issues with Confluence, and the advice on Performance Tuning has not helped, you can always ask us for help. Performance issues can be hard to diagnose, however, and we often spend a lot of time going back and forth looking for more information about what may be causing Confluence to be slow for you. The best way to get a speedy resolution to your issue is to provide this information up front.

Please gather all of the information listed below and include it in your support request, even if you think you have a good idea what's causing the problem. That way we don't have to ask for it later.

System Information

Confluence Server

• Take a screenshot of Confluence's Administration → System Information (or save the page as HTML)
• Take a screenshot of Confluence's Administration → Cache Statistics (or save the page as HTML)
• Find out the exact hardware Confluence is running on
  • How many CPUs? What make and model? What MHz?
  • How much memory is installed on the machine?
  • How much memory is assigned to Confluence's JVM? (i.e. what are the -Xmx and -Xms settings for the JVM?)
  • What other applications are being hosted on the same box?

Confluence Content

• How many users are registered in Confluence?
• How many spaces are there in your Confluence server?
• Approximately how many pages? (Connect to your database and perform 'select count(*) from content where prevver is null and contenttype = 'PAGE'')

The Database

• What is the exact version number of Confluence's database server?
• What is the exact version number of the JDBC drivers being used to access it? (For some databases, the full filename of the driver JAR file will suffice)
• Is the database being hosted on the same server as Confluence?
• If it is on a different server, what is the network latency between Confluence and the database?
• What are the database connection details? How big is the connection pool? If you are using the standard configuration this information will be in your confluence_cfg.xml file. Collect this file. If you are using a Data source this information will be stored in your application server's configuration file, collect this data.

User Management

• Are you using external user management or authentication? (i.e. JIRA or LDAP user delegation, or single sign-on)
• If you are using external JIRA user management, what is the latency between Confluence and JIRA's database server?
• If you are using LDAP user management:
  • What version of which LDAP server are you using?
  • What is the latency between Confluence and the LDAP server?

Diagnostics

Observed Problems

• Which pages are slow to load?
  • If it is a specific wiki page, attach the wiki source-code for that page
• Are they always slow to load, or is the slowness intermittent?

Access logs

• Enable user access logging, including redirecting the logs to a separate file
  • You can run this file through a log file analyser such as AWStats, or manually look through for pages which are slow to load.

Profiling and Logs

• Enable Confluence's built-in profiling for long enough to demonstrate the performance problem using Troubleshooting Slow Performance Using Page Request Profiling.
  • If a single page is reliably slow, you should make several requests to that page
  • If the performance problem is intermittent, or is just a general slowness, leave profiling enabled for thirty minutes to an hour to get a good sample of profiling times
• Find Confluence's standard output logs (which will include the profiling data above). Take a zip of the entire logs directory.
• Take a thread dump during times of poor performance

CPU Load

• If you are experiencing high CPU load, please install the YourKit profile and attach two profiler dumps taken during a CPU spike. If the CPU spikes are long enough, please take the profiles 30-60 seconds apart.

Next Step

Open a ticket on http://support.atlassian.com and attach all the data you have collected. This should give us the information we need to track down the source of your performance problems and suggest a solution. Please follow the progress of your enquiry on the support ticket you have created.

If your site is non-responsive, please use our Live Support during business hours once you have created the ticket to escalate your problem.