@mint @dsm https://eientei.org/objects/fafbe44b-51a9-469e-a9cc-95a4d877693c -- here is a writeup and here are pleroma patches and migrations: https://gitlab.eientei.org/eientei/pleroma/-/tree/upstream-flake

Since it needs to migrate object ids to time-ordered snowflakes and rearrange some of the denormalized fields to properly partition the tables anyway, it also changes a bunch of queries to take advantage of new layout, as many joins became easier. Migration includes both up and down, so it is possible to rollback, but migration back from partitioned layout wasn't very well tested, especially after new objects were inserted. Eientei runs on this for a couple of months now, so it is more or less reasonable in terms of completeness. But to be something more than just 15% of overhead, it requires understanding of what you're doing. Then sure, moving all older rows to a partition on cheaper or even a networked storage is possible.