Uploaded image for project: 'C# Driver'
  1. C# Driver
  2. CSHARP-1829

Concurrency benchmark unable to utilize all available cores

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.3
    • Component/s: Performance
    • Labels:
    • 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 driver doesn't perform as well as other comparable drivers in a benchmark related to overall throughput. It doesn't appear that individual operations are slower as noted by other benchmarks, but a general slowness when under a heavy load of concurrent operations over an extended period of time.

      Original

      @MongoDB Europe16 John Page talked about the performance of all the different drivers in different languages.

      It was observed out the C# driver was significantly slower than it should be, since you would expect it to be in the same league as the Java driver (and it is a factor of X slower).

      The result was similar in .NET 4.6 and .NET Core.

      So I'm creating this issue to help keep track of what can be done to "fix" this apparent problem/bug.

            Assignee:
            Unassigned Unassigned
            Reporter:
            nicof Nico Francois
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: