NuoDB Ops System Overview Graphs
This series of graphs are a collection of duplicate graphs for overview purposes.
This graph is a duplicate of the Memory usage graph.
Memory used will tend to the set memory value for the
There will be a saw-tooth pattern where garbage collection will run.
Flat lines must be investigated.
This graph plots the total CPU used per Storage Manager (SM) and Transaction Engine (TE) normalized to max 100%.
The CPU usage per engine should not exceed 80% of max CPU. Anything over 80% must be investigated.
This graph plots the rate of transactions committed per second. This is similar to Commits in SQL group of graphs.
Typically, the transaction rate depends on the workload. A heavier workload will mean a higher transaction rate. Longer periods where individual TEs have a high transaction rate may need investigation.
The sum of all the transactions per second across all TEs and the total number of TEs.
Typically, the aggregate transaction rate depends on the workload. A heavier workload will mean a higher aggregate transaction rate. Longer periods where there is a high aggregate transaction rate may need investigation.
The number of client connections per TE. Similar to Connections in SQL graphs.
Typically, client connections per SM and TE depend on application configuration and should be evenly spread across all TEs (except for tie-breaker TEs).