BryceStevenWilley
commented
2 years ago Did a little more digging here:
- DB usage is up to 8GB with 3 jurisdictions (TX does seem to be the larger outlier)
- optional services take up 6.45 GB (811 MB index)
- filing takes up 1.412GB (202MB index)
- filing components take up 449MB (73MB index)
- all other tables are less than 80MB, I expect those to scale fine. When we hit our max 8 or so Tyler jurisdictions, that will be maybe close to 20 GB as is. That won't fit on my local computer for dev, lol
Splitting optional services gets us down to ~2.4GB + index, and shirking some additional columns that don't need to be text gets us to 1.98GB + index.
For the filing and filing component tables, shrinking the other columns reduces disk usage by 181MB and 116MB respectively.
Will need to take some dumps and example tables, this is a much bigger migration than previous DB schema upgrades. It shouldn't be critical right now, but it will be very soon.
The optional service codes are by far the largest tables, and now that we are running 3 (soon to be 6) different domains (jurisidiction and stage / test), it's starting to take up a lot of space. The issue is that for each individual optional service, there are 1000's of filing codes, and each service / filing code combination takes up another row and repeats the whole name / all the other data points. We need to split up the table into two to reduce the extra disk usage (we're at 7.3GB for 2.5 domains), and should also improve performance too.
The key will be to figure out a way to decouple the exact codes zip we get from Tyler into the two different tables, without changing how we handle all the tables too much.