- 🇺🇸United States effulgentsia
I added ✨ Add way to "intern" large field item values to reduce database size by 10x to 100x for sites with many entity revisions and/or languages Active as another possible approach.
When saving new revisions for every change, we end up with a lot of duplicated data on a site. This is a good things because it gives you a full audit trail, however it also means a much larger database. Rather than performance issues as such, it tends to increase database dump and restore times first.
Consider providing a way to 'prune' older revisions. We could add a 'minor revision' flag similar to wikipedia's, or trim by age, or trim by the number of revisions in the past for a particular entity.
Could also decide we don't want this in core and defer the logic to a contrib module.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I added ✨ Add way to "intern" large field item values to reduce database size by 10x to 100x for sites with many entity revisions and/or languages Active as another possible approach.