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

Considerable performance drop

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.2.9
    • Affects Version/s: 2.2.8
    • Component/s: MongoDB 3.2
    • Environment:
      node.js v4.2.3
      MongoDB Cluster with 4 shards (3.2.8)

      After deploying a new version of our application server we noted a strong increase in response times of the service.
      Preliminary analyses in NewRelic showed that most of the time is spend in the 'mongodb' section of the route. Please have a look at the attached screenshots.
      Checking in MongoDB Cloud Manager, we couldn't see any increase in queries or query performance to the cluster.
      The only MongoDB related change was a minor bump of the MongoDB Node.js native driver from 2.2.6 to 2.2.8. After pinning the driver version to 2.2.6 the situation normalized again and we are back to the usual performance, as you also can see in the attached screenshots.

      Please let me know if I can help with any further detail.

      Cheers,
      Lars

        1. mongodb-history-user-find-one.png
          mongodb-history-user-find-one.png
          264 kB
        2. mongodb-likes-toarray.png
          mongodb-likes-toarray.png
          274 kB
        3. mongodb-overall-performance.png
          mongodb-overall-performance.png
          231 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            lars@iamat.com Lars Jacob
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: