Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6706

Use CPU baseline and ping benchmark to scale results against transient variance

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.14.3, bson-6.10.4
    • Affects Version/s: None
    • Component/s: None
    • Not Needed

      Use Case

      As a... Node.js engineer
      I want... a benchmark that tests the CPU performance
      So that... I have a scale of how hosts or runtime may relate to the performance of my code

      Dev Experience

      • A new CPU bound benchmark

      Dependencies

      • None

      Risks/Unknowns

      • We should make sure the results are stable by running it many times chrono-co-located

      Acceptance Criteria

      Implementation Requirements

      • Use the primes result to scale the ping benchmark
      • Use the ping benchmark to scale the rest of the driver benchmarks
      • Use the primes result to scale the bson benchmarks
      • Potentially, use new benchmarks for general serialization/deserialization
      • Add relevant tags corresponding to the contexts created in NODE-6736

      Testing Requirements

      • unit test, spec test sync, etc

      Documentation Requirements

      • DOCSP ticket, API docs, etc

      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

            Assignee:
            warren.james@mongodb.com Warren James
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: