Details
-
Task
-
Status: Accepted
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- related to
-
TOOLS-1856 use a memory pool in mongorestore
-
- Accepted
-