Setting maxConnecting=500 causes 70% CPU time in garbage collection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Go Drivers
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      I'm seeing a large amount of time being spent in golang garbage collection for this simple ping workload is this expected or am I doing something drastically wrong? I see this even without goroutines, just running 100 golang processes for looping on ping

        1. image-2025-01-21-08-44-42-415.png
          image-2025-01-21-08-44-42-415.png
          302 kB
        2. image-2025-01-21-08-45-01-261.png
          image-2025-01-21-08-45-01-261.png
          613 kB
        3. oncpu.svg
          572 kB

            Assignee:
            Preston Vasquez
            Reporter:
            Daniel Hill
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - 5 weeks
                5w
                Remaining:
                Remaining Estimate - 5 weeks
                5w
                Logged:
                Time Spent - Not Specified
                Not Specified