This is an automated email from the ASF dual-hosted git repository.

orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 7eb89618 Update index.md
7eb89618 is described below

commit 7eb89618cb14fae92904a9674c141a6ac85a97d4
Author: Francesco Nigro <[email protected]>
AuthorDate: Thu May 25 16:01:05 2023 +0200

    Update index.md
---
 content/blog/2023/05/camel-4-performance-improvements/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2023/05/camel-4-performance-improvements/index.md 
b/content/blog/2023/05/camel-4-performance-improvements/index.md
index 2dd87654..f9000347 100644
--- a/content/blog/2023/05/camel-4-performance-improvements/index.md
+++ b/content/blog/2023/05/camel-4-performance-improvements/index.md
@@ -21,7 +21,7 @@ The JVM issue 
[JDK-8180450](https://bugs.openjdk.org/browse/JDK-8180450), known
 
 # Unveiling Performance Insights
 
-Our investigation highlighted a significant concern related to the 
instructions per second (IPS) when utilizing the disruptor component in earlier 
versions of Camel (e.g., Camel 3.14, 3.18, and 3.20). Notably, we observed IPS 
values of approximately 0.71, 0.81, and 0.77, respectively. These numbers 
indicated a performance bottleneck where the CPU experienced delays due to 
memory I/O.
+Our investigation highlighted a significant concern related to the 
instructions per cycle (IPC) when utilizing the disruptor component in earlier 
versions of Camel (e.g., Camel 3.14, 3.18, and 3.20). Notably, we observed IPC 
values of approximately 0.71, 0.81, and 0.77, respectively. These numbers 
indicated a performance bottleneck where the CPU experienced delays due to 
memory I/O.
 
 To delve deeper, we employed the 
[type-pollution-agent](https://github.com/RedHatPerf/type-pollution-agent), 
which successfully generated a comprehensive report detailing the affected 
conversions. This report 
[validated](https://issues.apache.org/jira/browse/CAMEL-19058) our suspicions 
and [emphasized the need](https://issues.apache.org/jira/browse/CAMEL-19060) 
for immediate attention to overcome the performance 
[barriers](https://issues.apache.org/jira/browse/CAMEL-19319). Notably, we d 
[...]
 

Reply via email to