Subscriber Database Sizing Configuration
You can use the configuration parameters in create_config.py to configure the subscriber database. If you are unsure about the number of balances, devices, and services each subscriber will have or the number of subscribers, groups, or users in your data domain, use the default values.
Subscriber Data Configuration Parameters lists the information required to configure the subscriber database.
| Parameter | Description | Default Value |
|---|---|---|
| Number of Subscribers | The maximum number of subscribers in your subscriber base. This value is used internally to configure MATRIXX Engine queue sizes, database sizes, and internal memory structures. Set this value
higher than your total subscriber base to handle future additions. create_config.info question: How many subscribers do you want to support? |
100000 |
| Average Number of Balances | The average number of currency balances, asset balances, and meters in each subscriber's wallet. This value is used internally to determine
the size of the Balance Set database. create_config.info question: What is the average number of balances per subscriber? |
4 |
| Average Number of Devices | The average number of devices owned by each subscriber. This value is used internally to determine the size of the subscriber database. create_config.info question: What is the average number of devices per subscriber? |
2 |
| Average Number of Login Devices | The average number of login devices that a customer must have for user identification and authorization of service usage. This parameter is for access from a device not registered to the
subscriber, such as a computer, and is used internally to determine the size of the subscriber database. create_config.info question: What is the average number of login devices per subscriber? Note: To create a login device, this value must be greater than zero.
|
0 |
| Average Size of Login Device | The average size of a login device object in bytes. This value is used internally to set the configuration. If this value is too small, you might not be able to add objects. If the value
is too large, memory is wasted. To determine the correct size for your system, look for "object size" in the mtx_debug.log file after you shut down
the engine. To disable this feature, enter 0 for this value. create_config.info question: What is the average size of a login device object in bytes? |
300 Bytes |
| Initial Size of Login Device | The initial size of the login device object. This value is used internally to allocate the object at initial creation. If the value is too small and the object size grows at each update,
the activity database becomes fragmented. If the value is too large, memory is wasted. To determine the correct size for your system, look for "object size" in the
mtx_debug.log file after you shut down the engine. To disable this feature, enter 0 for this value.
create_config.info question: What is the initial size of a login device object in bytes? |
200 Bytes |
| Number of Groups | The maximum number of groups in your subscriber base. This value is used internally to determine the size of the subscriber database and
internal memory structures. create_config.info question: How many groups do you want to support? Note: Set the value greater than the default value, for example, to 2000, to avoid group creation errors.
|
1000 |
| Number of Users | The number of users that a customer must have for user identification and authorization of service usage. create_config.info question: How many users do you want to support? |
100000 |
| Average Size of User Objects | The average size of a user object in bytes. This value is used internally to set the configuration. If the value is too small, you might not be able to add objects. If the value is too
large, memory is wasted. To determine the correct size for your system, look for "object size" in the mtx_debug.log file
after you shut down the engine. To disable this feature, enter 0 for this value. create_config.info question: What is the average size of a user object in bytes? |
300 Bytes |
| Initial Size of User Object | The initial size of the user object. This value is used internally to allocate the object at initial creation. If the value is too small and the object size grows at each update, the
activity database becomes fragmented. If the value is too large, memory is wasted. To determine the correct size for your system, look for "object size" in the
mtx_debug.log file after you shut down the engine. To disable this feature, enter 0 for this
value. create_config.info question: What is the initial size of a user object in bytes? |
300 Bytes |