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 fc60fc36 Fixed missing header element on the recent blog post
fc60fc36 is described below
commit fc60fc36efcd435849c7031b157465fbfc7f67f1
Author: Otavio Rodolfo Piske <[email protected]>
AuthorDate: Fri May 26 10:25:34 2023 +0200
Fixed missing header element on the recent blog post
---
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 90f5c7e8..64154aa9 100644
--- a/content/blog/2023/05/camel-4-performance-improvements/index.md
+++ b/content/blog/2023/05/camel-4-performance-improvements/index.md
@@ -11,7 +11,7 @@ preview: "Hunting performance monsters on the back of a Camel"
We are thrilled to share the remarkable advancements in the performance of
Apache Camel 4, achieved through our diligent efforts in addressing a critical
JVM issue (JDK-8180450). In this article, we will delve into the details of our
investigation, the tools employed, and the subsequent optimizations that have
propelled Apache Camel 4 to new heights of speed and efficiency.
-Identifying the Performance Challenge:
+# Identifying the Performance Challenge
The JVM issue [JDK-8180450](https://bugs.openjdk.org/browse/JDK-8180450),
known for its potential performance penalties during type checking, became our
focal point. To gain a comprehensive understanding of the issue, we extensively
utilized diagnostic tools such as perf stat, perf c2c, the async-profiler, and
the type-pollution-agent, as recommended in the [JDK-8180450 troubleshooting
documentation](https://github.com/RedHatPerf/type-pollution-agent/blob/master/benchmarks/WHATIF.md).
