Optimize event table

[ewinkler]

Need to manage volume of data stored in the event table. Most of the information in the table is really only relevant for a short period of time but has potential value for auditing. Options

1. Archive records greater than N days old so that they minimize volume in the database.
2. Use a different structure entirely for storing?

[pvenka]

The size of the table core_event in mds for your refernce. This site is active since March 10th.
There have been around 150 encounters added.

mysql> SELECT TABLE_NAME, table_rows, data_length, index_length, round(((data_length + index_length) / 1024 / 1024/1024),2) "Size in GB" FROM information_schema.TABLES WHERE table_schema = "mds" ORDER BY (data_length + index_length) DESC;
+----------------------------+------------+-------------+--------------+------------+
| TABLE_NAME | table_rows | data_length | index_length | Size in GB |
+----------------------------+------------+-------------+--------------+------------+
| core_event | 165690 | 6714195968 | 15056896 | 6.27 |
| mrs_requestlog | 201452 | 5668864 | 0 | 0.01 |
| django_admin_log | 5900 | 1589248 | 278528 | 0.00 |
| core_observation | 965 | 212992 | 327680 | 0.00 |
| mrs_savedprocedure | 69 | 278528 | 32768 | 0.00 |