Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5900 Improve perf of large document logging
  3. NODE-6452

Improve Performance of Command Monitoring

XMLWordPrintableJSON

    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 6.13.0
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • 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?

      The first part of performance hits during logging actually occurs during the command monitoring stage, even with logging disabled. Here's an example with no command monitoring and command monitoring:

       

      largeDocBulkInsert megabytes_per_second n/a 31.0216885085 11.7661826882
      largeDocInsertOne megabytes_per_second n/a 44.369467752 14.4284864574

       

      First step to improve logging will be to improve this first step, most notably around the command deep copy.

            Assignee:
            warren.james@mongodb.com Warren James
            Reporter:
            durran.jordan@mongodb.com Durran Jordan
            Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: