[
https://issues.apache.org/jira/browse/CAMEL-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689601#comment-17689601
]
Otavio Rodolfo Piske edited comment on CAMEL-19060 at 2/16/23 8:10 AM:
-----------------------------------------------------------------------
Supporting links for interpreting the reports:
* [Detecting false
sharing|https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/monitoring_and_managing_system_status_and_performance/detecting-false-sharing_monitoring-and-managing-system-status-and-performance#detecting-false-sharing-with-perf-c2c_detecting-false-sharing]
from Red Hat Enterprise Linux 8.
* Joe Mario's [blog post|https://joemario.github.io/blog/2016/09/01/c2c-blog/]
about detecting false sharing.
Other relevant links:
* A blog post about [Type Check
Scalability|https://redhatperf.github.io/post/type-check-scalability-issue/]
(which may be related).
was (Author: orpiske):
Supporting links for interpreting the reports:
* [Detecting false
sharing|https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/monitoring_and_managing_system_status_and_performance/detecting-false-sharing_monitoring-and-managing-system-status-and-performance#detecting-false-sharing-with-perf-c2c_detecting-false-sharing]
from Red Hat Enterprise Linux 8.
* Joe Mario's [blog post|https://joemario.github.io/blog/2016/09/01/c2c-blog/]
about detecting false sharing.
Other relevant links:
* A blog post about [Type Check
Scalability|https://redhatperf.github.io/post/type-check-scalability-issue/]
(which may be related).
*
> 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, 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.
> 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].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
