Difference between revisions of "CyberShake Database Server Requirements"
From SCECpedia
Jump to navigationJump to search (→Moment) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Below are a list of requirements for CyberShake database servers, hosted at CARC. | 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 === | === Configuration === | ||
| Line 9: | Line 9: | ||
==== Hardware ==== | ==== Hardware ==== | ||
| − | * | + | *128 GB RAM |
*6-8 TB hard drive space, ideally SSD+redundancy (RAID 5?) | *6-8 TB hard drive space, ideally SSD+redundancy (RAID 5?) | ||
| Line 15: | Line 15: | ||
*Linux OS | *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). | *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: | *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: | ||
<pre> | <pre> | ||
innodb_file_per_table = 1 | innodb_file_per_table = 1 | ||
| − | innodb_buffer_pool_size = | + | innodb_buffer_pool_size = 102G |
innodb_buffer_pool_instances = 8 | innodb_buffer_pool_instances = 8 | ||
query_cache_type = 0 | query_cache_type = 0 | ||
| − | tmp_table_size = | + | tmp_table_size = 64M |
| − | max_heap_table_size = | + | max_heap_table_size = 64M |
innodb_log_file_size = 2G | innodb_log_file_size = 2G | ||
</pre> | </pre> | ||
| Line 29: | Line 32: | ||
*screen | *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 === | === Configuration === | ||
| Line 37: | Line 40: | ||
==== Hardware ==== | ==== Hardware ==== | ||
| − | * | + | *At least 64 GB RAM |
*6-8 TB hard drive space, ideally SSD+redundancy (RAID 5?) | *6-8 TB hard drive space, ideally SSD+redundancy (RAID 5?) | ||
| Line 43: | Line 46: | ||
*Linux OS | *Linux OS | ||
| + | *Well-known MySQL port (3306) externally accessible | ||
*MariaDB, current stable release (10.11.2 as of 3/7/23). | *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: | *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: | ||
<pre> | <pre> | ||
innodb_file_per_table = 1 | innodb_file_per_table = 1 | ||
| − | innodb_buffer_pool_size = | + | innodb_buffer_pool_size = 52G |
innodb_buffer_pool_instances = 8 | innodb_buffer_pool_instances = 8 | ||
| − | query_cache_type = | + | query_cache_type = 1 |
| − | tmp_table_size = | + | query_cache_size = 64M |
| − | max_heap_table_size = | + | tmp_table_size = 64M |
| + | max_heap_table_size = 64M | ||
innodb_log_file_size = 2G | innodb_log_file_size = 2G | ||
</pre> | </pre> | ||
*SQLite, current stable release (3.41.0 as of 3/7/23). | *SQLite, current stable release (3.41.0 as of 3/7/23). | ||
*screen | *screen | ||
Latest revision as of 20:30, 13 March 2023
Below are a list of requirements for CyberShake database servers, hosted at CARC.
Contents
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
