- 1 Introduction
- 2 Getting Started
3 Technical Architecture and Guide
- 3.1 GridDB Technical Overview
- 3.2 Key Container Model
- 3.3 TQL
- 3.4 CRUD Operations
- 3.5 Transactions and ACID
- 3.6 Indexes
- 3.7 Storage Architecture
- 3.8 Replication & Distribution
- 3.9 Sharding
- 4 Data Modeling
5 Sample Applications
- 5.1.1 Introduction
- 5.1.2 GridDB Basics
- 5.1.3 Preparation: Environment (server)
- 5.1.4 Preparation: Environment (client)
- 5.1.5 Preparation: Connecting GridDB
- 5.1.6 Schema definition
- 5.1.7 Container Create / Delete
- 5.1.8 Register Collection
- 5.1.9 Data Retrieval
- 5.1.10 Data Deletion
- 5.1.11 Collection Modification
- 5.1.12 Data Registration
- 5.1.13 Data Retrieval
- 5.1.14 Time-Series Data Deletion
- 5.1.15 Change of Time-Series Container
- 5.1.16 TQL
- 5.1.17 Trigger (REST)
- 5.1.18 Trigger (JMS)
- 5.1.19 Multi-Put
- 5.1.20 Multi-Query
- 5.1.21 Multi-Get
- 5.1.22 Meta-information
- 5.1 Basics
- 6 Administration
- 7 Drivers & Integrators
2.1 System Requirements
Checking the Required Resources
GridDB is a scale-out database that -- unlike a conventional database -- pre-planning of the system design and sizing is not required in order to achieve non-stop operation. However, the following points should be considered as guidelines in the initial system design:
- Memory usage
- Number of nodes in a cluster
- Disk usage
The estimation method is explained in sequence below.
Functions to increase the capacity by using external storage devices such as SSDs, etc. have not been considered in calculating the memory size below. Please check with our service desk for estimation if these functions are used.
Total memory usage
1. Predict the amount of data to be stored in the application. Estimate the following:
- Data size of row
- Number of rows to be registered
2. Estimate the memory required to store those estimated data.
Memory capacity used = row data size × no. of registered rows ÷ 0.75 + 8 × no. of registered rows × (assigned index number + 2) ÷ 0.66 (byte)
3. Perform a similar estimation for all collections created and used in the application. The total sum becomes the amount of memory required in the GridDB cluster.
Total memory usage = the sum of memory usage in all collections
Note: please consider this number as the minimum requirement, as the memory usage also depends on update frequency.
Number of Nodes Constituting a Cluster
Estimate the required no. of nodes used in GridDB. In the example below, it is assumed that one node is executed in one machine.
First, make an assumption of the memory required per machine.
In addition, make an assumption of the no. of replicas to create. The no. of replicas is given as a GridDB configuration value.
Estimate the size of the file to be created in GridDB, and the disk capacity required for the machine to execute a node. Two types of files should be created; a checkpoint file and a transaction log file.
The memory usage of individual node is determined as follows:
Individual memory usage = (total memory usage * no. of replicas) ÷ no. of nodes (byte)
The size of the checkpoint file is estimated as follows based on this numerical value.
File size = Individual memory usage * 2 (byte)
In addition, as the transaction log life size is dependent on the update frequency of the application, the following data is thus predicted.
Row update frequency (times/sec)
Furthermore, the checkpoint interval is assumed. The checkpoint interval is given as a GridDB configuration value.
- Checkpoint interval
The default value of the checkpoint interval is 1200 sec (20 minutes).
The transaction log file size is estimated as follows based on these numerical values:
File size = row data size * row update frequency * checkpoint interval (byte)
The individual disk usage is estimated as follows.
Individual disk usage = Transaction log file size + checkpoint file size
[Point to note]The size of the checkpoint file expands depending on the data capacity. However, please note that once it has expanded, the file size will not be reduced, even if some of data in the container or row gets deleted. Empty space can be re-used after data is deleted.