On 10/6/24 10:22, Jan Høydahl wrote:
Such a low number generally doesn't make much sense, other than perhaps very special collection where you want to trigger commits immediately, however maxTime:1 would normally be a better setting. Perhaps the one creating that config intended the default to be -1?
FWIW I have a bunch of DIH replacement scripts that post documents in batches with `commit=true`, and I ran timings when setting them up. On the standalone "dev" node I get the best throughput w/ batch size around 5K docs, on the production 2-node "cloud" w/ numreplicas=2 and numshards=1: 2K docs.
Committing after a single document simply takes forever. The default on 8.11.2 has no maxDocs in either `autoCommit` setting. Dima
