Databases Reference
In-Depth Information
We enabled the
mod_status
module and configured the server's status page.
The server status page provides the following monitoring statistics:
• The number of on-going requests
• The number of idle worker threads
• Process details
• The total access requests
• The number of requests served per second
During a load test, if it is found that most of the time there are no idle workers and
requests are not going through, it is recommended to resize Apache threads / max
client configuration. If the problem still persists, requests might not be processed
because the Liferay Portal server is taking more time to respond. If the memory
usage is consistently high, it is recommended to reduce the Apache thread / max
client pool size.
Monitoring the database server
Liferay Portal is database agnostic. We can configure any JDBC-supported database
server with the Liferay Portal server. In our reference architecture, we have used
MySQL. Most of the database products provide their own monitoring and tuning
tools. In this section we will discuss which items should be monitored during
load tests.
CPU and memory usage
CPU and memory usage of the database server must be monitored during a load
test to find any performance bottlenecks. As discussed in the previous section, the
easiest way to monitor CPU and memory is through the TOP command. But it is
recommended to configure SNMP-based tools such as Nagios for CPU and memory
usage monitoring. There could be multiple reasons of high CPU or memory usage.
After the load test, further investigation will be required to find out the root cause
of this.
Slow queries
It is very important to identify database queries that are taking more time. It is also
important to find out database queries that are executed many times during the load
test. Every database product provides one way or an other to get slow queries or the
top
n
queries.
