Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5677 Remove the MessageStream abstraction from the connection layer
  3. NODE-5771

Benchmark the new Connection class

XMLWordPrintableJSON

    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.4.0
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • 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 to know the benchmark data of the ModernConnection API
      So that I can optimize or account for what ever differences there are in performance

      User Impact

      • Hot path all I/O travels through this API

      Dependencies

      • Server.command / Monitor / RTTPinger / connect

      Unknowns

      • Should we isolate the new API in a simulated benchmark? - I do not know how valuable this may end up being. I think if the existing benchmarks reveal a regression, this would be good to start identifying bottlenecks
      • Can we run a patch where we migrate the driver to the new connection class entirely and see what our existing benchmarks say? - I think this is a very good starting point

      Acceptance Criteria

      Implementation Requirements

      • Run the benchmarks using the new Connection class
        • This should be after monitoring is also capable of using the new API so it is entirely the new implementation
      • Gather results, and compare against waterfall benchmarks

      Testing Requirements

      • None

      Documentation Requirements

      • None

      Follow Up Requirements

      • Identify bottlenecks, file tickets to correct or alleviate

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Durran Jordan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: