That's true, good point, ermouth. Yeah, set the concurrency to 1, and also to ensure it won't be picked up by other channels (slack vs ratio), so maybe set the concurrency to 0 for those.
Besides the docs on the site there is also an smoosh operator's guide in https://github.com/apache/couchdb/blob/main/src/smoosh/operator_guide.md that might have some more details about scheduling compactions, though there is a chance some might be outdated a bit. -Nick On Sun, Jul 28, 2024 at 4:23 PM ermouth <ermo...@gmail.com> wrote: > Thanks for the prompt response! > > To clarify further: does [smoosh.%db_related_channel%] concurrency=2 mean > one still might need 1Gb even with 2 shards? > > ermouth > > > On Sun, Jul 28, 2024 at 11:11 PM Nick Vatamaniuc <vatam...@gmail.com> > wrote: > > > Hi ermouth, > > > > Yeah that should reduce the maximum disk space needed for compaction and > > might be a good reason to split the shards into smaller ones. > > > > Cheers, > > -Nick > > > > > > On Sun, Jul 28, 2024 at 1:43 PM ermouth <ermo...@gmail.com> wrote: > > > > > Hi! > > > > > > Does sharding affect minimal required disk space during DB compaction > > > operation? > > > > > > I mean if one has 1Gb in 1 shard it would likely require ~1Gb free disk > > > space to perform compaction. If a DB had 2 shards ~500Mb each, would it > > > reduce minimal required free disk space to ~500Mb? > > > > > > Thanks, > > > ermouth > > > > > >
