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

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      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

        1.
        		 Report normalized benchmarks in the driver and tag benchmarks correctly NODE-6755 Sub-task Closed Warren James 6.14.0
        2.
        		 Report normalized benchmarks in bson and tag benchmarks correctly NODE-6756 Sub-task Closed Warren James bson-6.11.0
        3.
        		 Support adding tags to perf.send results in bsonBench NODE-6757 Sub-task Closed Warren James  
        4.
        		 Remove dependence on bson from bson-bench NODE-6772 Sub-task Closed Warren James bson-bench-0.0.1
        5.
        		 Move creation of install location to Suite.run in bson-bench NODE-6782 Sub-task Closed Warren James  
        6.
        		 Move tags into metrics.metadata subdocument in bson-bench NODE-6806 Sub-task Closed Warren James dbx-js-tools-1.0.0
        7.
        		 Move tags to metrics.metadata subdocument in driver benchmarks NODE-6807 Sub-task Closed Warren James  
        8.
        		 Post driver benchmark results to endpoint so tags are used NODE-6843 Sub-task Needs Verification Neal Beeken  

            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: