The drop-and-recreate sweep measures each partition configuration on a newly built index. I would add a second phase after sustained inserts and deletes, using the same query set, because an index’s steady-state partition shape can differ from its clean-build shape.
Record the write workload and maintenance state, then compare recall and latency after the churn settles and while it is active. That gives the partition-size choice an operational test beyond the initial CSV curve. It would also help distinguish a setting that works for a mostly static reference corpus from one that remains useful for frequently updated application context.
Sai Kiran Kshatriya