CyberShake Database Server Requirements

Below are a list of requirements for CyberShake database servers, hosted at CARC.

Moment

Moment is the production database for CyberShake, used to keep track of CyberShake runs, store intensity measures, and produce hazard curves.

Configuration

Hardware

• 128 GB RAM
• 6-8 TB hard drive space, ideally SSD+redundancy (RAID 5?)

Software

• Linux OS
• Well-known MySQL port (3306) externally accessible for read-only access
• Writes can be restricted to CARC servers
• Project filesystem doesn't need to be mounted once DB is set up
• MariaDB, current stable release (10.11.2 as of 3/7/23).
• Ideally, user scottcal would be able to edit the /etc/my.cnf.d/* MariaDB config files, and restart the DB server. If not possible, please set the following values:

    innodb_file_per_table = 1
    innodb_buffer_pool_size = 102G
    innodb_buffer_pool_instances = 8
    query_cache_type = 0
    tmp_table_size = 64M
    max_heap_table_size = 64M
    innodb_log_file_size = 2G

• SQLite, current stable release (3.41.0 as of 3/7/23).
• screen

Focal

Focal is the user-facing CyberShake database server. It is the database used by the CS Data Access Tool, as well as the database used for user queries. It should be optimized for fast read access.

Configuration

Hardware

• At least 64 GB RAM
• 6-8 TB hard drive space, ideally SSD+redundancy (RAID 5?)

Software

• Linux OS
• Well-known MySQL port (3306) externally accessible
• MariaDB, current stable release (10.11.2 as of 3/7/23).
• Ideally, user scottcal would be able to edit the /etc/my.cnf.d/* MariaDB config files, and restart the DB server. If not possible, please set the following values:

    innodb_file_per_table = 1
    innodb_buffer_pool_size = 52G
    innodb_buffer_pool_instances = 8
    query_cache_type = 1
    query_cache_size = 64M
    tmp_table_size = 64M
    max_heap_table_size = 64M
    innodb_log_file_size = 2G

• SQLite, current stable release (3.41.0 as of 3/7/23).
• screen