2016 CyberShake database migration
To clarify terminology:
"Input data": Rupture data, ERF-related data, sites data. This data is shared between studies.
"Run data": What parameters are used with each run, timestamps, systems, study membership. A run is only part of a single study.
"Output data": Peak amplitudes data
Goals of DB Migration
- Provide improved read performance for users of CyberShake data
- Separate production data from data from completed studies
- Permit easy extension to support UGMS web site
Status of DB resources following migration
- Swapped hardware between moment and focal
- On read-only server, multiple DBs with Study 15.4 and Study 15.12 data
- On production server, keep Study 15.12 and 15.4
- Migrate older studies to alternative format, delete from production server.
Detailed Procedure for CyberShake DB Migration
- Run mysqldump on entire DB on focal. Generate dumpfiles for all the input data, each study's output and runs data, and the runs and output data which is not part of a study.
- Delete database on moment.
- Reconfigure DB on moment (single file per table, etc.)
- Load all files into DB on moment using the InnoDB engine; confirm they are present.
- Delete database on focal
- Load input data, Study 15.12, Study 15.4 onto focal for read-only access, using the MyISAM engine.
- Swap names of focal and moment so we don't have to change all our scripts.
Once this is done, we can finalize the alternative format we want. We may want to test SQLite to see if it can handle a large study.
Since the input data is much smaller (~100x) than the output data, we will keep a full copy of it with each study. It would be much more time intensive to identify which subset of runs data and input data applies just to the study and the extra space needed to keep it all is trivial. For each study, we will only keep the runs data for runs which are associated with that study.
