Databases Reference
In-Depth Information
An example of sizing calculations
We learned about the reference hardware and benchmark results. Now, let's size
the deployment architecture for a sample project.
Sample performance requirements
The example Portal solution should be able to handle 15,000 concurrent requests.
This is the only requirement that we received from the customer, and we need
to size our initial deployment architecture based on that.
Sizing calculations
Login
is the most resource-consuming operation in a Liferay-based portal. Also, the
login use case takes care of authentication as well as rendering of the home page,
which is displayed after authentication. We have not received any use case-specific
performance needs. So for sizing, we can refer to the benchmark results of the Login
with Legacy Simulator scenario. According to the results of this benchmark test, one
Liferay Portal application server can handle 6,300 concurrent login requests. So to
handle 15,000 concurrent login requests, we will need three Liferay Portal application
servers. Generally, the load on the web server is less than 50 percent of application
servers. Hence, we can derive the number of web servers as half of the application
servers. So in our case, we will need two web servers (3 application servers/2). For the
database server as per our reference architecture, it is recommended to have a master-
slave database server. This calculation is valid for similar hardware configurations
as it was used in the benchmark performance test. Hence, we need to use the same
hardware configuration for the application server, web server, and database servers.
This calculation is an initial sizing calculation. More accurate
sizing calculations can be done only after the system is
developed and load testing is performed.
The Documents and Media Library
architecture
Documents and Media Library is one of the most important functionality of Liferay
Portal. It allows users to manage documents, images, videos, and other types of
documents. This functionality is designed in such a way that metadata is stored in the
database, while actual files are stored on pluggable repository stores. Liferay Portal
ships with various built-in repository stores. In this section, we will learn about these
repository stores and the best practices associated with them.
