Confluence 5.6 のサポートは終了しています。
ドキュメントの最新バージョンを確認してください。
Use native database tools to assess the impact of your database. If you'd like to check what Confluence is doing from it's side, you can enable SQL logging. If you analyze thread dumps, as this is done in general Troubleshooting Confluence hanging or crashing guide, you may find the kinds of threads like this:
"http-8080-Processor150" daemon prio=1 tid=0x08543368 nid=0x11aa in Object.wait() [0x665a4000..0x665a51b0] at java.lang.Object.wait(Native Method) - waiting on <0x83140488> (a com.mchange.v2.resourcepool.BasicResourcePool) at com.mchange.v2.resourcepool.BasicResourcePool.awaitAcquire(BasicResourcePool.java:968) at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:208) - locked <0x83140488> (a com.mchange.v2.resourcepool.BasicResourcePool)
These threads are waiting for a database connection. It could be that the database is not performing optimally, or it may just need tuning for allowing more connection threads. Both are discussed below.
SQL Server 2000, Oracle 9i, and MySQL with 3.1 drivers are among some of the issues with database performance. Ensure you are using updated versions of databases and their drivers.
Atlassian does not offer specific recommendations on hardware for database performance. Use good judgment and native OS and database tools for your assessment.
Confluence has improved database performance over time. You'll want to make sure you have all the latest, if you're getting hung threads waiting for db connections.
With 2.10 and later, Confluence includes database indices bundled. Confluence 2.10 automatically creates the necessary database indexes when you upgrade. If you are not on 2.10, you may have run the ddl manually during the upgrade process. To check, you can look against these.
This is described in the knowledge base article Confluence Slows and Times out During Periods of High Load due to DB Connection Pool.
If a database is getting overloaded, you can prevent it from crashing Confluence by Configuring a database query timeout.