When switching the VisualEditor API to DirectParsoidClient, we will start using the stashing backend configured in the ParsoidCacheConfig setting under the StashType key, which defaults to the backend configured in MainStash setting.
This is currently configured to be:
$wgObjectCaches['db-mainstash'] = [ 'class' => 'SqlBagOStuff', 'cluster' => 'extension2', 'dbDomain' => 'mainstash', 'globalKeyLbDomain' => 'mainstash', 'tableName' => 'objectstash', 'multiPrimaryMode' => true, 'purgePeriod' => 100, 'purgeLimit' => 1000, 'reportDupes' => false ];
It is not clear that this backend has sufficient capacity for handling stashing for VE edits across all sites. We may want to configure a simillar backend on the cluster that holds the ParserCache.
Based on the metrics about the stash backend used by RESTBase, we estimate a need for about 140GB of storage capacity for the VE edit stash. This is based on the measurement of 100 writes per second and a 24 hours TTL, with an average of 20KB per entry.
See also {T309016: Determine storage requirements for stashing parsoid output for VE edits}
