Moment-carc configuration: Difference between revisions
From SCECpedia
Jump to navigationJump to search
Created page with "This page documents the configuration requirements for moment-carc, the CyberShake production database hosted by CARC. == Functionality == moment-carc should support the fol..." |
|||
| Line 19: | Line 19: | ||
== Database configuration == | == Database configuration == | ||
We would like to use the following settings in the mariadb-server.cnf file: | |||
<pre> | |||
innodb_file_per_table = 1 | |||
innodb_buffer_pool_size = 112G (should be 16 GB less than the available system memory) | |||
innodb_buffer_pool_instances = 8 | |||
query_cache_type = 0 | |||
tmp_table_size = 32M | |||
max_heap_table_size = 32M | |||
innodb_log_file_size = 2G | |||
</pre> | |||
== Network configuration == | == Network configuration == | ||
Revision as of 20:19, 28 April 2022
This page documents the configuration requirements for moment-carc, the CyberShake production database hosted by CARC.
Functionality
moment-carc should support the following:
- Relational database to host CyberShake input data, run status, run metadata, and store commonly used intensity measures and hazard curves.
Hardware
- 2 TB of local storage for the database (SSD, if possible). Current database size on moment is ~1.5 TB, but some of that should be migrated to focal, as the intent is that focal serves as the access point for completed studies.
- At least 64 GB RAM (current moment has 128 GB)
Software (installed by CARC)
- Latest production version of MariaDB (10.6.7 as of 4/27/22)
Software (installed by SCEC)
Database configuration
We would like to use the following settings in the mariadb-server.cnf file:
innodb_file_per_table = 1 innodb_buffer_pool_size = 112G (should be 16 GB less than the available system memory) innodb_buffer_pool_instances = 8 query_cache_type = 0 tmp_table_size = 32M max_heap_table_size = 32M innodb_log_file_size = 2G
