Optimizing Arize Phoenix Telemetry: Pruning DB for Efficiency

Heyyy guys, we were using Arize phoenix telemetry - docker image Now we've used it so much that we've a lot of traces and now phoenix UI is taking too long to respond We know we can delete all the traces from UI but we were looking for a way to prune the DB And then intention is to make it a cron job which runs every Sunday so that it deletes the traces and we only keep like 2 weeks of traces or say 1 month of traces only Any suggestions?