CRJAZ2284W The database performance measurement took 2559 ms. A value greater than 2500 ms is considered slow and might indicate a problem with the database.

The diagnostic is running a series of simple database operations and timing them. These include a time for ping, read, and write to the database. The tool measures  the time for the server to communicate with the database and execute a simple SQL statement. This doesn't include the time for the browser/thick client to communicate with the server.

Use the web client, create a health check widget. This widget runs a ping test against the database. This captures the roundtrip time from the server to the database and back. It doesn't run an SQL statement against the database. This test will isolate the network time from the database time. If the ping time is acceptable, then you'll need to look at the database load.

If the diagnostic behaves differently under load then when the system is not under load, the database server may be the bottleneck. If this is the case the queries, etc, aren't completing because the database is busy processing other requests, and can't get to yours, or because there is contention for resources blocking the requests.