Camel
  1. Camel
  2. CAMEL-4531

Expose workerCount parameter of Netty NioServerSocketChannelFactory in Camel-Netty

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.8.1
    • Fix Version/s: 2.8.2, 2.9.0
    • Component/s: camel-netty
    • Labels:
      None
    • Environment:

      ALL

    • Patch Info:
      Patch Available
    • Estimated Complexity:
      Unknown

      Description

      Camel-netty component did not implement oio model of netty, we can only use nio one, however it uses default workerCount parameter from Netty, which is cpu_core_threads*2.

      This is far from enough when the underlying app is a little bit slow, e.g. a traditional transactional application. In this situation NioWorker threads become an obvious bottle neck.

      I think that exposing workerCount is a very practical yet effective way for one to broaden the usage scenario of camel-netty in various network communication/application environment.

      I add a workerCount parameter in the configuration, one can use it in the Endpoint URL: "netty:tcp://0.0.0.0:1111?...&workerCount=256&...". I leave the default value to 0 so that one can use Netty default policy by omit the param.

      I have tested the patch in a 2 core(4 Threads) machine, using 256 workers, it significantly improves the performance by 15 times, than the default parameter of only 8 workers, while CPU usage only increase 5 times.

      1. workerCount-2.9.patch
        2 kB
        edge wang
      2. workerCount.patch
        2 kB
        edge wang

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Willem Jiang
            Reporter:
            edge wang
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development