-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
ALL
-
-
Query Execution 2021-06-28, Query Execution 2021-07-12, QE 2022-04-04, QE 2022-04-18, QE 2022-05-02, QE 2022-05-16, QE 2022-05-30, QE 2022-06-13, QE 2022-06-27, QE 2022-07-11, QE 2022-07-25, QE 2022-08-08, QE 2022-08-22
When accessing a field in a Document, it's expected that the internal caching will add some overhead to the memory footprint. However when the accessed path contains nested documents, it appears that the reported size double counts the values in the sub-objects. The impact may not be incredibly severe, given that it has "approximate" in the method name, but there are several aggregation stages that rely on this size to decide whether to spill to disk.
- is related to
-
SERVER-71824 Estimate error and speed of doc.getApproximateSize() vs. doc.toBson().objsize()
- Closed
-
SERVER-61281 Fix underflow when accounting for Document size in query memory tracker
- Closed