Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-90929

Investigate the impact of boost::optional<BSONObj> on translateEquality performance

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization

      translateEquality of IndexBounds aims to save work by re-using the existing _backingBSON from the corresponding MatchExpression.

      By making _backingBSON optional, translateEquality must ensure that the provided bson object is not only valid but also holds a value.

      With the most recent patch, this functionality is done using a boost::optional. However, boost::optional may incur performance penalty compared to a simpler bool/value solution.

      This ticket aims to investigate the performance impact of boost::optional on this function call and update the implementation accordingly.

            Assignee:
            Unassigned Unassigned
            Reporter:
            matt.olma@mongodb.com Matt Olma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: