Interstage Shunsaku Data Manager Operator's Guide - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX - |
Contents
Index
![]() ![]() |
Appendix D Estimating Resources | > D.3 Estimating Resources for the Director |
This section explains the formulas for estimating how much memory directors will use.
The shared memory requirement is shown below.
Definition unit |
Variable elements |
Size (bytes) |
---|---|---|
The area for storing command information |
Fixed |
1,000,000 |
The formulas for estimating local memory are shown below.
Definition unit |
Variable elements |
Size (bytes) |
---|---|---|
Amount of memory used during startup |
The maximum number of search requests that can be received at the same time (*1) The total number of records |
4,500,000 + 150,000 x The maximum number of search requests that can be received at the same time + (154 + The maximum number of search requests that can be received at the same time) x The total number of records |
Variable amount of memory used for search requests |
The maximum number of search requests that can be received at the same time (*1) Average number of hits (*2) Average search expression size Average return expression size Average sort expression size The total number of records Standard record size (in bytes) (*3) |
(1,100 + Average search expression size + Average return expression size + Average sort expression size + Standard record size + 40 x Average number of hits) x The maximum number of search requests that can be received at the same time |
Variable amount of memory used for update requests |
Average number of updated records within a transaction (*4) The maximum number of transactions (*5) Standard record size (in bytes) (*3) |
(16,500 + (128 + Standard record size) x Average number of updated records within a transaction) x The maximum number of transactions |
*1) This is specified in the MultiMax parameter in the director environment file.
*2) Specify the number of XML documents that match the search condition.
*3) Specify the standard record size to be searched or added/updated.
*4) Specify the average number of records to be updated per transaction.
*5) Specify the maximum number of transactions to be executed simultaneously.
If the direct access function is used, add the following memory estimations to the local memory.
The formulas for estimating local memory when using the director function are shown below.
Definition unit |
Variable Elements |
Size (bytes) |
---|---|---|
Amount of memory used during startup |
|
(12 + 36 x The number of direct access key definitions (*1)) The total number of records |
The area for storing direct access key information |
|
The number of direct access key definitions from |
Variable amount of memory used for the direct search requests |
|
(1,100 + (40 + Average size of direct access key) x The number of direct access keys to be specified + Average size of return expression + Standard record size (in bytes) x The maximum number of direct search requests that can be received at the same time |
Variable amount of memory used for direct update requests and direct delete requests |
|
(16,500 + Average size of direct access key x The number of direct access keys to be specified + (128 + Standard record size (in bytes) x Average number of updated records within a transaction) x The maximum number of transactions |
*1) Specify the number of direct access key names that are specified at the DirectKeyListFile parameter in the director environment file, and the direct access key definition file.
*2) Specify the average size of direct access keys in each direct access key definition. Average size refers to the average value of the size of direct access keys in each direct access key definition in each record.
*3) Set the information of 'the number of direct access key coefficient' according to the detail of the direct access key.
*4) Specify the maximum number of records of the direct search requests that can be received at the same time.
*5) Specify the average size of the direct access key to be specified. Average size refers to the average value of the size of the direct access key to be specified.
*6) Specify the number of direct access keys that are specified in the direct search request once.
*7) Specify the standard record size to be searched, added or updated.
*8) Specify the average number of records to be updated in 1 transaction.
*9) Specify the maximum number of transactions that can be executed in the same time.
Direct Access Key Coefficient
Detail of direct access key |
Value of direct access key coefficient |
---|---|
There are many changes in the value at the last part of the key. |
0.4 - 0.6 |
There are many changes in the value at the first part of the key. |
0.6 - 0.8 |
There are many changes in value at the entire of the key. |
0.8 - 1.0 |
The actual amount of memory used may be more than the result of estimation according to the detail in the direct access key (degree of difference). Therefore, use the actual machine to measure and check the actual amount of memory used.
Example Calculation
An example calculation for local memory is shown below.If the variable elements are as follows:
- The maximum number of search requests that can be received at the same time: 100
- The total number of records: 100,000
- Average number of hits: 100 (records)
- Average search expression size: 1,024 (bytes)
- Average return expression size: 1,024 (bytes)
- Average sort expression size: 1,024 (bytes)
- Maximum number of transactions: 100
- Average number of update records within a transaction: 10
- Standard record size: 4,000 (bytes)
Amount of Memory used during Startup
4,500,000 + 150,000 x 100 + (154 + 100) x 100,000 = 44,900,000 bytes (approx. 43 MB)Variable Amount of Memory used for Search Requests
(1,100 + 1,024 + 1,024 + 1,024 + 4,000 + 40 x 100) x 100 = 1,217,200 bytes (approx. 1.2 MB)Variable Amount of Memory used for Update Requests
(16,500 + (128 + 4,000) x 10) x 100 = 5,778,000 bytes (approx. 5.6 MB)If the direct access is used, add the following estimation result to the estimation result above.
If the variable elements that is added when using the direct access function are as follows:
The number of direct access key definitions: 3 (KEY1, KEY2, KEY3)
- Average size of direct access key in each direct access key definition:
Average value of the size of KEY1: 4 bytes
Average value of the size of KEY2: 6 bytes
Average value of the size of KEY3: 12 bytes- The direct access key coefficient in each direct access key definition:
Coefficient value of KEY1: 0.4
Coefficient value of KEY2: 0.6
Coefficient value of KEY3: 0.4- The number of direct search requests that can be received at the same time: 100
- Average size of direct access key specified for the direct search: 12 bytes
- The number of direct access keys specified for the direct search: 10
- The maximum number of transactions for the direct update: 100
- Average size of direct access key specified for the direct update: 12 bytes
- The number of direct access keys specified for the direct update: 10
- Average number of updated records within a transaction: 1
Amount of memory used during startup (additional amount for direct access function)
(12 + 36 x 3) x 100,000 = 12,000,000 bytes (approx. 12 MB)The area for storing direct access key information
(0.4 x 2 x 100,000 x [4 - log(100,000)] x 76) + (0.6 x 2 x 100,000 x [6 - log(100,000)] x 76) + (0.4 x 2 x 100,000 x [12 - log(100,000)] x 76) = 57,760,000 bytes (approx. 55 MB)Variable amount of memory used for the direct search requests
(1,100 + (40 + 12) x 10 + 1,024 + 4,000) x 100 = 664,400 bytes (approx. 0.7 MB)Variable amount of memory used for direct update requests and direct delete requests
(16,500 + 12 x 10 + (128 + 4,000) x 1) x 100 = 2,074,800 bytes (approx. 2 MB)
Contents
Index
![]() ![]() |