Thanks to new data expiring strategies like bug 1667051, we're able to delete more than 100 million (no longer needed) rows from the database. However, the database doesn't seem to give that freed up space back to the operating system. Other specialists complain about this [on SO as well](https://stackoverflow.com/questions/1270944/mysql-innodb-not-releasing-disk-space-after-deleting-data-rows-from-table?answertab=oldest#tab-top) & suggest various techniques & utilities such as the [OPTIMIZE statement](https://dev.mysql.com/doc/refman/8.0/en/optimize-table.html). We need to ask our DBAs to take care of this aspect.
Bug 1682580 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks to new data expiring strategies like bug 1667051, we're able to delete more than 100 million (no longer needed) rows from the database. However, the database doesn't seem to give that freed up space back to the operating system. Other specialists complain about this [on SO as well](https://stackoverflow.com/questions/1270944/mysql-innodb-not-releasing-disk-space-after-deleting-data-rows-from-table?answertab=oldest#tab-top) & suggest various techniques & utilities such as the [OPTIMIZE statement](https://dev.mysql.com/doc/refman/8.0/en/optimize-table.html). We need to ask our DBAs to take care of this aspect. **Jira link:** https://jira.mozilla.com/browse/FXP-1390