Scribd
Upload
46 views2 pages

Comments: Database Performance Check

Check the database connection pool usage and ensure it is not at maximum capacity. Test all datasources and check for any long running queries or database locks that could impact performance. Monitor server CPU utilization, swap usage, and Java garbage collection to ensure the system has necessary resources and Java heap is being properly managed to prevent out of memory errors. Also check that WebSphere nodes and the domain manager are synchronized and inspect Java logs for issues like hung threads or connection pool exhaustion.

Uploaded by

Sathish Pillai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
46 views2 pages

Comments: Database Performance Check

Check the database connection pool usage and ensure it is not at maximum capacity. Test all datasources and check for any long running queries or database locks that could impact performance. Monitor server CPU utilization, swap usage, and Java garbage collection to ensure the system has necessary resources and Java heap is being properly managed to prevent out of memory errors. Also check that WebSphere nodes and the domain manager are synchronized and inspect Java logs for issues like hung threads or connection pool exhaustion.

Uploaded by

Sathish Pillai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Database Performance Check Comments

Connection Pool Usage

Datasource Test

Long running DB queries/DB Locks

Server Performance Check Comments

Monitor CPU utilization

Monitor Swap Usage

Monitor Heap Garbage Collection


Performance
Websphere JVM Check Comments

Check if Node and DMGR are in Sync

Check JVM logs for Hung thread/Connection


pool exhaust/OutOfMemory
Description

The Connection High should not be the


same as the JDBC pool size.

Check if all the datasource is passing.

Check DB for any long running query. Check for


any DB locks.

Description

Monitor CPU utilization to ensure there


are no CPU contention.
If there is not enough space left on the
swap device (or paging file), the OS could
prevent another process from starting or
Monitoring
in some cases heapbeGC performance
forced is
to kill running
critical for
processes. performance and availability.
For example, if the amount of heap free
after a GC is continually increasing and
approaching the maximum heap size, the
JVM could experience OutOfMemory
exceptions.
Description

You might also like