Databases Reference
In-Depth Information
The Deployment sizing approach
In the previous section, we learned about the Liferay Portal reference architecture.
The reference architecture is generic in nature. It can be used as a reference to define
an architecture that is more specific to a project. One of the important activities in
defining a specific architecture is
sizing
. We need to be sure of the number of Liferay
Portal application servers or web servers to meet performance expectations. In the
beginning of the project when the system is yet to be developed, it is impossible
to size the architecture with 100 percent accuracy. Hence, the idea is to size the
architecture based on previous benchmarks, and then review the sizing during the
load testing phase when the system is ready. Liferay Inc. publishes the performance
benchmark for every major Liferay Portal release. It is a best practice to use this
benchmark as a reference and size the deployment architecture of the solution. In
this section, we will learn how to size the deployment architecture of the Liferay-
Portal-based solution based on Liferay's performance benchmark whitepaper.
This section refers to the Liferay Portal 6.1 performance white
paper published by Liferay Inc.. This whitepaper can be
accessed through the following URL:
http://discover.liferay.com/LP=13/?i=Liferay_
Portal_6.1
The first step of the sizing activity is to capture some of the basic non-functional
requirements. The following table provides a list of these questions. The answers to
these questions will act as parameters for sizing calculations.
No.
The requirement question
Mandatory?
Details
1
How many concurrent users will
log in at the same time?
Yes
Login is the most resource-
consuming use case in Liferay
Portal. It is very important
to know the answer to this
question.
2
What is the number of
concurrent users accessing the
Message Board functionality
including login?
No
The Liferay performance
benchmark report publishes
the result of this scenario.
If the project requirement
matches the scenario, we
can use this to size the
deployment architecture
more accurately.
