Optimize usage of Result type in Mongorestore

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 937

      It was discovered in mongo-tools/274, which solves TOOLS-1856, that over 90% of dynamic allocation occurs due to this line.

      As tfogo mentioned in a subsequent comment, there's no need for this – we can possibly refactor mongorestore to so that it doesn't constantly have to allocate a new Result object.

            Assignee:
            Unassigned
            Reporter:
            Hari Amoor (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: