Blog post featured image

Introduction

Apache Camel has always been committed to delivering top-notch performance. As the development of Camel 4 progressed, so did the dedication to enhancing its performance. In this blog post, we’ll explore the advances made in the pursuit of efficiency, focusing on key improvements introduced between Camel 4.1 and 4.2, with a few important improvements for the upcoming 4.3.

Camel 4.1: A Leap Forward in Type Conversion

One of the notable enhancements in Camel 4.1 was the introduction of a new type converter. While being slightly more strict, this converter proved to be simpler to maintain and offered a modest boost in speed. This change was not without its challenges, as some minor issues and bugs surfaced in the wake of these adjustments. However, the development community swiftly addressed these concerns, ensuring a smoother experience for users.

Camel 4.2: Optimizing for Peak Performance

Building on the momentum of Camel 4.1, version 4.2 brought about significant optimizations, particularly in the realm of type converter cache handling and resolution. The community also applied strategic micro-optimizations, designed to assist the JIT Compiler in effectively inlining code. Furthermore, attention was given to the platform-http-vertx component hot path, where inefficiencies were identified and rectified.

Quantifying the Gains: Performance Metrics

The tangible results of these optimizations are evident in the performance improvements across various Camel EIPs (Enterprise Integration Patterns).

Comparing Camel 4.1 and 4.2 to their predecessors, it’s clear that aggregator, content-based route, and filter EIPs run notably and consistently faster on the newer versions. For instance, the image below shows the result of just one of thousand of tests executed.

graph

In this test, Camel version 4.2.0 processed exchanges about 18% faster than Camel 4.0.2 when doing so through a content-based router.

Camel Platform HTTP Vert.x: A Highlight in Efficiency

The optimizations within the Platform HTTP Vert.x component delivered measurable performance gains.

In our tests, the throughput increased by approximately 5% from Camel 4.0 to 4.2.

graph

With the current development code, there are indications of further gains, which are likely to be caused by a newer version of Vert.X:

graph

The average response time exhibited a progressive decline: from 0.367ms in 4.0.3, to 0.345 ms in 4.2.0, stabilizing around the same value for the current development version with an average of 0.348 ms.

The numbers for Camel 4.1 show a significant decrease in performance due to a bug that caused a cache miss when trying to resolve a type converter. This bug was fixed in 4.2.0.

Note: an earlier version of these images contained an incorrect description on the labels. The images were updated to reflect the correct data.

Testing: Ensuring Reliability

The reliability of these performance enhancements was validated through rigorous testing methodologies. For core components, the Camel Load Tester project was employed, ensuring a comprehensive evaluation of the framework’s capabilities. The testing of Platform HTTP Vert.x components, on the other hand, leveraged Hyperfoil, a powerful benchmarking tool.

Micro-optimizations, scattered throughout the codebase, underwent meticulous scrutiny using JMH (Java Microbenchmark Harness). This thorough testing approach guarantees that each optimization contributes positively to the overall performance without introducing unforeseen issues.

All of our tests were performed executed using Java 17.0.9, running on Red Hat Enteprise Linux 9.3. The test system was a PowerEdge R640 with 2 Intel Xeon Silver 4116 CPUs, each with 12 cores, and 192 Gb of memory.

Looking Ahead: The Evolution Continues

As Camel progresses towards version 4.3.0, the commitment to performance remains unwavering. The community continues to explore innovative ways to enhance speed, efficiency, and overall user experience. Whether it’s refining existing features or introducing new optimizations, Apache Camel is dedicated to being at the forefront of integration frameworks, empowering developers to build seamless, high-performance applications.

In conclusion, the journey of Apache Camel is not just about feature-rich functionality but also about delivering a robust and performant framework. The advancements in Camel 4.1 and 4.2, coupled with the promising improvements in the upcoming 4.3.0 release, underscore the project’s commitment to excellence. As users embrace these updates, they can look forward to a more responsive and efficient integration experience with Apache Camel.

Hunting performance monsters on the back of a Camel

 , by

Introduction 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 The JVM issue JDK-8180450, known for its potential performance penalties during type checking, became our focal point.

Continue reading ❯

FEATURESCAMEL

Introducing the Resume API v2

 , by

The need to process larger quantities of data has been a growing concern and necessity within our community. For the last few releases we have been working to create mechanisms to simplify how our users can consume data at scale. Although Camel is no stranger to consuming data at scale, recent trends in computing and systems architecture introduce the need for behaviors that improve agility, speed and scalability when doing so.

Continue reading ❯

FEATURESCAMEL

Good bye camel-testcontainers! Hello Camel's test-infra

 , by

For Camel 3.16.0 we are removing the deprecated container-based test modules and replacing them with a new set of modules called Camel test-infra. They continue to support container-based tests via TestContainers, however they abstract the underlying test infrastructure. One of the great benefits for our project is that they allow us to more easily switch from container-based tests, to external instances. Previously, we would need to create a new test or implement a more complex design if we wanted to test both a container instance and an external service instance (i.

Continue reading ❯

FEATURESCAMEL

Upcoming changes to the consumer on Kafka component

 , by

We recently started to review, investigate and fix reliability issues with the Kafka component. As part of that, we refactored the code to avoid problematic concurrency patterns, remove calls to deprecated Kafka client code and simplify the overall maintainability of the code. This led to many changes in the internal implementation of the component, which we will talk about in this blog post. Motivation The ground work related to these changes can be traced back to the following set of issues reported on our Jira.

Continue reading ❯

FEATURESCAMEL