Sync Strategies

Choosing batching, concurrency, and conflict behavior.

Batching

By default Nimbus waits 2 seconds after the last detected change before starting an upload, so a burst of edits becomes one batch instead of many small ones. Tune this with:

nimbus config set batchDelay 5s

Concurrency

concurrency (in nimbus.config.json) controls how many files upload in parallel. Raise it on fast connections, lower it if you’re hitting provider rate limits:

{ "concurrency": 8 }

Conflict resolution

When the same file changed both locally and at the target since the last sync, Nimbus’s default strategy is newest-wins, comparing modification timestamps. Other strategies:

nimbus config set conflictStrategy manual

Large files

Files over 100 MB are automatically uploaded in multipart chunks. To change the threshold:

nimbus config set multipartThreshold 50MB