3.10 Estimating resources

Estimating the size of the shared memory

The following describes how to estimate the size of the shared memory used by the web server and the performance tracer.

Size of the shared memory used by the web server

The size of the shared memory used by the web server is calculated as described below.

Note that the size of the shared memory used by the web server is the same as the size of shared memory files.

Size of shared memory used by web server = 7,168 * ThreadsPerChild

Legend:

ThreadsPerChild: Number of threads (bytes) to be started as servers

Size of the shared memory used by the performance tracer

The size of the shared memory used by the performance tracer is calculated as described below.

Note that the size of the shared memory used by the performance tracer is the same as the size of shared memory files.

Size of shared memory used by performance tracer = value_specified_for_PrfTraceBufferSize * 1,024 + 18,496

Legend:

value_specified_for_PrfTraceBufferSize: Trace buffer size (bytes) for the performance tracer retained in the shared memory

Estimating the number of processes

The following describes how to estimate the number of processes for the Java EE server, the web server, and performance tracer.

Number of Java EE server processes

The number of resident Java EE server processes is calculated as follows:

Number of Java EE server resident processes = number_of_domain_management_servers
 + number_of_server_instances

Number of web server processes

The number of web server processes is calculated as follows:

Number of web server processes = control_processes + server_processes
 + CGI_processes + rotatelogs_processes + rotatelogs2_processes

Legend:

control_processes: 1

server_processes: 1

CGI_processes: Number of server threads

rotatelogs_processes: Twice the number of rotatelogs programs specified for the CustomLog directive, the ErrorLog directive, the HWSRequestLog directive, and the TransferLog directive

rotatelogs2_processes: Twice the number of rotatelogs2 programs specified for the CustomLog directive, the ErrorLog directive, the HWSRequestLog directive, and the TransferLog directive

Number of performance tracer processes

The number of resident performance tracer processes is 1.

Estimating the number of threads

The following describes how to estimate the numbers of threads for the Java EE server, the web server, and performance tracer.

Number of Java EE server threads

The number of threads to be used by the Java EE server is calculated as follows:

Legend:

Dt: Total number of threads for each domain management server process

SIt: Total number of threads for each server instance process

m: Number of domain management server processes

n: Number of server instance processes

To calculate the total number of threads for each domain management server process (Dt) and the total number of threads for each server instance process (SIt), use one of the following formulas:

Legend:

Tm: Maximum value for thread pools

Tn: Number of threads that do not belong to thread pools. Among these threads, 44 threads are created by default by, for example, the domain administration server and server instance.

m: Number of thread pools for domain management servers

n: Number of thread pools for server instances

Number of web servers threads

To calculate the number of threads used by the web server, use the following formula:

Number of threads used by the web server = 3 + number_of_rotatelogs_processes
 + number_of_rotatelogs2_processes
 + value_specified_for_ThreadsPerChild_directive_(number_of_server_threads)

Number of performance tracer threads

The number of threads used by performance tracer is 10.

Estimating the number of file descriptors

It is not necessary to estimate the number of file descriptors, because the number of file handles cannot exceed the maximum number of file handles set for the OS by default (16,581,375).

Estimating database capacity

If you want to use the EJB timer service and Java Batch as functions of Application Server, DBMS is required. DBMS stores the DDL file where table information is defined. Based on the table information of this DDL file, estimate the database capacity.

The following table shows where the DDL files necessary for estimation are stored.

Table 3‒4: DDL file locations

No.	Target	Storage directory	File name	DBMS
1	EJB timer service	installation_directory_for_Application_Server/javaee/glassfish/lib/install/databases	ejbtimer_oracle.sql	Oracle