Use Case

As a... (who is this for)
I want... (what is the desired change)
So that... (why is the change desired)

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• Add primes baseline benchmark task
• Add the alerting-benchmark tag to the following benchmark results (deserialize and serialize)
  • Flat bson
  • Deep bson
  • Full bson
  • objectid_array_1000
  • double_array_1000
  • Int32_array_1000
  • long_array_1000
  • string_array_1000
  • binary_array_1000
  • ObjectId.isValid
    • Isvalid_wrong_string_length
    • Isvalid_invalid_hex_at_start
    • Isvalid_invalid_hex_at_end
    • Isvalid_valid_hex_string
• For the granular benchmarks, add tags to each benchmark based on each type

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• Add test readme note about the perf contexts and tags we use

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward