Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-75514

baseline CPU usage and disk reads increased significantly with >6.0.3

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      MongoDB v6.0.3 on a t3.micro (x86_64) running Ubuntu 18.04.2 LTS with a gp3 volume for data storage and an ext4 filesystem
    • Product Performance
    • ALL

      baseline CPU usage and disk reads increased significantly with >6.0.3

      Hi! We are running MongoDB v6.0.3, when the database was upgraded to v6.0.5, the following changes were noted on the server and disk volume (without changes to the application using the database):

      • the average CPU usage went up from about 4.5% to 30%
      • average read bandwidth increased from about 100kiB/s to 4MiB/s
      • read throughput increased from 2 ops/s to 700 ops/s
      • average read size decreased from 40kiB/s to 5kiB/s

      The same changes were observed in v6.0.4 and downgrading to v6.0.3 resolved the issue.

      Was something changed in v6.0.4 that may have cause this? I'm trying to figure out what I need to change in order to support the newer versions without the huge performance hit.

        1. updateOnetest.js
          2 kB
        2. Screenshot 2023-03-30 at 12.41.54 PM.png
          Screenshot 2023-03-30 at 12.41.54 PM.png
          77 kB
        3. image-2023-06-06-14-15-39-342.png
          image-2023-06-06-14-15-39-342.png
          190 kB
        4. image-2023-05-17-20-16-42-067.png
          image-2023-05-17-20-16-42-067.png
          27 kB
        5. image-2023-05-17-20-16-34-127.png
          image-2023-05-17-20-16-34-127.png
          12 kB
        6. image-2023-05-10-14-23-37-933.png
          image-2023-05-10-14-23-37-933.png
          60 kB
        7. image-2023-05-10-14-22-20-430.png
          image-2023-05-10-14-22-20-430.png
          44 kB
        8. image-2023-05-09-10-08-24-250.png
          image-2023-05-09-10-08-24-250.png
          44 kB
        9. image-2023-05-09-09-54-15-302.png
          image-2023-05-09-09-54-15-302.png
          62 kB
        10. image-2023-05-09-09-52-24-063.png
          image-2023-05-09-09-52-24-063.png
          50 kB
        11. image-2023-05-09-09-52-02-605.png
          image-2023-05-09-09-52-02-605.png
          59 kB
        12. image-2023-05-09-09-49-58-689.png
          image-2023-05-09-09-49-58-689.png
          61 kB
        13. image-2023-05-09-09-48-07-236.png
          image-2023-05-09-09-48-07-236.png
          59 kB
        14. image-2023-05-08-15-47-22-326.png
          image-2023-05-08-15-47-22-326.png
          46 kB
        15. image-2023-05-08-15-40-30-396.png
          image-2023-05-08-15-40-30-396.png
          35 kB
        16. image-2023-05-08-15-19-52-496.png
          image-2023-05-08-15-19-52-496.png
          45 kB
        17. image-2023-05-08-14-49-54-836.png
          image-2023-05-08-14-49-54-836.png
          49 kB
        18. image-2023-05-04-15-32-47-938.png
          image-2023-05-04-15-32-47-938.png
          215 kB
        19. image-2023-04-05-12-53-43-841.png
          image-2023-04-05-12-53-43-841.png
          119 kB
        20. benchmark-run_1.jpg
          benchmark-run_1.jpg
          179 kB
        21. 6.0.4-right-after-query.log
          27 kB
        22. 6.0.3-right-after-query.log
          15 kB

            Assignee:
            chris.kelly@mongodb.com Chris Kelly
            Reporter:
            jordan.baczuk@qnergy.com Jordan Baczuk
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: