[SERVER-15702] Use RecordIterator::dataFor over Collection::dataFor when doing table scans Created: 17/Oct/14  Updated: 25/Oct/14  Resolved: 17/Oct/14

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.7.7
Fix Version/s: 2.7.8

Type: Improvement Priority: Minor - P4
Reporter: John Esmet Assignee: Unassigned
Resolution: Done Votes: 0
Labels: pull-request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Participants:

 Description   

We should optimize record store scans by accessing documents using the record iterator itself, which may be iterating over a data structure that co-locates disklocs (record ids) and the corresponding record's data.



 Comments   
Comment by Githook User [ 17/Oct/14 ]

Author:

{u'username': u'esmet', u'name': u'John Esmet', u'email': u'john.esmet@gmail.com'}

Message: SERVER-15702 During collection scans, read the document from the
RecordIterator instead of the Collection. This way the RecordIterator
class can optimize document fetch for disklocs that were just returned.

Closes #829

Signed-off-by: Benety Goh <benety@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/c3e58867a942565309cae3c04c642437d36edb2c

Generated at Thu Feb 08 03:38:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.