Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-912

Stop tying number of parallel collections to numThreads in mongodump

    • Type: Icon: New Feature New Feature
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.9
    • Affects Version/s: None
    • Component/s: mongodump
    • None
    • Server Tools A (10/09/15)
    • Needed

      Unless we have a strong reason to keep them coupled, it is awkward to have the number of collections we dump in parallel be tied to the hidden --numThreads flag. NumThreads internally tunes the Go runtime to multiplex goroutines across N operating system threads. This is orthogonal to dumping a collection, which is almost entirely I/O bound.

      As a naming suggestion, I think it would make most sense to mimic the j / numParallelCollections naming from mongorestore.

      Even if we still want to leave the flag undocumented/hidden, we should decouple it from numThreads.

            Assignee:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Reporter:
            kyle.erf Kyle Erf
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: