4.2.1 Estimating the disk capacity required for EADS servers

This subsection explains how to estimate the disk capacity required for EADS servers.

If you will be using disk caches and two-way caches, add the required disk capacity estimated in 4.4 Estimating the sizes of cache files to the following values that are estimated here.

Total size of log files per EADS server
Size of store data files

Organization of this subsection

(1) Estimating the total size of log files per EADS server
(2) Estimating the size of store data files
(3) Estimating the total size of log files and store data files per EADS server

(1) Estimating the total size of log files per EADS server

The following shows the formula for estimating the total size of log files per EADS server.

Total size of log files per EADS server (megabytes) =

a + b + c + d + e

Explanation of the variables

a: Size of message log files output by an EADS server

b: Size of message log files output during command execution

c: Size of Java log files

d: Size of statistics files

e: Size of user message log files

The following subsections explain the formulas used to estimate the sizes of individual log files.

For details about the log files managed by the EADS servers, see 7.4.1 Types of log files.

(a) Size of message log files output by an EADS server

The following shows the formula for estimating the size of message log files output by an EADS server.

Size of message log files output by an EADS server (megabytes) =

size of a message log file (bytes) [Figure] 1,024²

[Figure] number of message log files + 100

Size of a message log file (bytes):: eads.logger.message.filesize parameter value in the server properties
Number of message log files:: eads.logger.message.filenum parameter value in the server properties

Round up the value to the next full megabyte because the value of the eads.logger.message.filesize parameter in the server properties is specified in bytes.

(b) Size of message log files output during command execution

The following shows the formula for estimating the size of message log files output during command execution.

Size of message log files output during command execution (megabytes) =

size of a message log file (bytes) [Figure] 1,024²

[Figure] number of message log files

Size of a message log file (bytes):: eads.command.logger.message.filesize parameter value in the command properties
Number of message log files:: eads.command.logger.message.filenum parameter value in the command properties

Round up the value to the next full megabyte because the value of the eads.command.logger.message.filesize parameter in the command properties is specified in bytes.

(c) Size of Java log files

The following shows the formula for estimating the size of Java log files.

Size of Java log files (megabytes) =

(size of a Java log file (megabytes)

[Figure] number of Java log files) 2 + 32

Size of a Java log file (megabytes):: eads.java.log.filesize parameter value in the server properties
Number of Java log files:: eads.java.log.filenum parameter value in the server properties

(d) Size of statistics files

The following shows the formula for estimating the size of statistics files.

Size of statistics files (megabytes) =

(size of statistics files (eads_stats.csv)

+ size of statistics files for caches (eads_cache_stats.csv)

+ size of statistics files per range (eads_store_stats.csv)

+ size of statistics files for user functions (eads_function_stats.csv))

[Figure] 1,024²

The following shows the formulas for estimating the sizes of individual statistics files.

■ Size of statistics files (eads_stats.csv)

Size of statistics files (eads_stats.csv) (bytes) =

{1,024 + 1,024 [Figure] (86,400 statistics output interval)}

[Figure] (number of statistics files to be acquired + 1)

■ Size of statistics files for caches (eads_cache_stats.csv)

Size of statistics files for caches (eads_cache_stats.csv) (bytes) =

{1,024 + (2,048

[Figure] (number of memory caches + (number of disk caches + number of two-way caches) data multiplicity))

[Figure] (86,400 statistics output interval)}

[Figure] (number of statistics files to be acquired + 1)

■ Size of statistics files per range (eads_store_stats.csv)

[Figure] When using the total data restriction function

Size of statistics files per range (eads_store_stats.csv) (bytes) =

{1,024 + (2,048

[Figure] (data multiplicity + number of disk caches + number of two-way caches))

[Figure] (86,400 statistics output interval)}

[Figure] (number of statistics files to be acquired + 1)

[Figure] When not using the total data restriction function

Size of statistics files per range (eads_store_stats.csv) (bytes) =

■ Size of statistics files for user functions (eads_function_stats.csv)

Size of statistics files for user functions (eads_function_stats.csv) (bytes) =

{1,024 + (2,048 [Figure] number of user functions)

[Figure] (86,400 statistics output interval)}

[Figure] (number of statistics files to be acquired + 1)

Statistics output interval:: eads.statistics.interval parameter value in the server properties
Number of statistics files to be acquired:: eads.statistics.filenum parameter value in the server properties

(e) Size of user message log files

The following shows the formula for estimating the size of user message log files.

Size of user message log files (megabytes) =

size of a user message log file (bytes) [Figure] 1,024²

[Figure] number of user message log files

Size of a user message log file (bytes):: eads.user.logger.filesize parameter value in the server properties
Number of user message log files:: eads.user.logger.filenum parameter value in the server properties

Round up the value to the next full megabyte because the value of the eads.user.logger.filesize parameter in the server properties is specified in bytes.

To Page Top

(2) Estimating the size of store data files

The following shows the formula for estimating the size of store data files.

Size of store data files (megabytes) =

(key size per data item^#1 + value size per data item^#1 + 100)

[Figure] number of data items stored per EADS server^#2

[Figure] (maximum number of store-data-file generations that are output when the eztool export command is executed

+ maximum number of store-data-file generations that are output when the eztool stop command is executed + 1)

[Figure] 1,024²

#1

This is the size obtained after serialization.

In C, this is the size obtained by adding 10 bytes to the value size specified in the EADS client.

#2

This includes the number of data items copied for redundancy.

Maximum number of store-data-file generations that are output when the eztool export command is executed:

eads.admin.backup.exportCommand.generation.maxNum parameter value in the shared properties

Maximum number of store-data-file generations that are output when the eztool stop command is executed:

eads.admin.backup.stopCommand.generation.maxNum parameter value in the shared properties

Important note: The management information is still stored even if data is exported to a store data file while there is no data in memory, in which case a maximum of four kilobytes are used. Therefore, the size of the store data file in use is never zero bytes.

For details about store data files, see 7.4.1 Types of log files.

To Page Top

(3) Estimating the total size of log files and store data files per EADS server

Add the values obtained in (1) Estimating the total size of log files per EADS server and (2) Estimating the size of store data files.

If you will be using disk caches and two-way caches, add the required disk capacity estimated in 4.4 Estimating the sizes of cache files.

To Page Top