Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-19060

Scalability ceiling: seda

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.18.5, 4.0-M1
    • 4.0-RC1
    • None
    • None
    • Unknown

    Description

      When using the Seda producer/consumer on a large core count machine, it seems that Camel's throughput peak at around 9 producer / 9 consumer threads and after that starts to decrease [1]. This seems to indicate some kind of coherence issue - the cost to keep the threads coherent exceeds the system's ability to handle the load / use the system's free capacity.

       

      1. This, of course, taking in consideration that the thread pool had been adjusted and the machine has enough capacity. Both of which were true.

      The attachments contains `perf` reports of the analysis of Camel 3.18.5, but similar patterns also happen w/ 4.0.0-M1. In particular, note the low "Instruction per cycle" reported on the attachment perf-stats.txt and the high incidence of Last Level Cache (LLC) misses to Remote Cache (HITM) in the attachment stats.txt.

      Attachments

        1. perf-stats.txt
          0.6 kB
          Otavio Rodolfo Piske
        2. stats.txt
          3 kB
          Otavio Rodolfo Piske

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            orpiske Otavio Rodolfo Piske
            orpiske Otavio Rodolfo Piske
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment