Multitenant configuration (2 tenants, 1 instance for every DI module, 1 partition for every DI topic):
module | configuration |
---|---|
mod-data-import | mod-data-import-2.8.0-SNAPSHOT.260 name: DB_MAXPOOLSIZE value: '5' name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties |
SRMmod-source-record-manager | mod-source-record-manager-3.7.0-SNAPSHOT.762 name: DB_MAXPOOLSIZE value: '15' name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties name: DB_RECONNECTINTERVAL value: '1000' name: DB_RECONNECTATTEMPTS value: '3' |
SRSmod-source-record-storage | mod-source-record-storage-5.6.3-SNAPSHOT.608594f name: DB_MAXPOOLSIZE value: '15' name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties |
mod-inventory | mod-inventory-20.1.0-SNAPSHOT.607 name: DB_MAXPOOLSIZE value: '5' name: JAVA_OPTIONS -XX:MaxRAMPercentage=85.0 -Dorg.folio.metadata.inventory.storage.type=okapi |
mod-inventory-storage | mod-inventory-storage-26.0.0 name: DB_MAXPOOLSIZE value: '5' name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 |
mod-di-converter-storage | mod-di-converter-storage-2.1.0-SNAPSHOT.9 name: DB_MAXPOOLSIZE value: '5' name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties |
...
Its described in
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
I created a task to deeply investigate the work of DI, its performance, and its use of resources:
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...