[
https://issues.apache.org/jira/browse/CAMEL-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689586#comment-17689586
]
Otavio Rodolfo Piske edited comment on CAMEL-19060 at 2/16/23 7:56 AM:
-----------------------------------------------------------------------
Some *hypothesis* that need to be investigated and tested:
* Additional / non-reported impacts due to CAMEL-19058
* Excessive locks and/or their granularity
* Maybe overhead due to multiple volatile variables causing cache invalidation
* False sharing
was (Author: orpiske):
Some *hypothesis* that need to be investigated and tested:
* Additional / non-reported impacts due to CAMEL-19058
* Excessive locks and/or their granularity
* Maybe overhead due to multiple volatile variables causing cache invalidation
> Scalability ceiling
> -------------------
>
> Key: CAMEL-19060
> URL: https://issues.apache.org/jira/browse/CAMEL-19060
> Project: Camel
> Issue Type: Task
> Affects Versions: 3.18.5, 4.0-M1
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Attachments: perf-stats.txt
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
