You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by or...@apache.org on 2021/09/24 08:36:03 UTC

[camel-website] branch main updated: Fixed a small typo on the Camel Kafka blog post (#634)

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 7f91cef  Fixed a small typo on the Camel Kafka blog post (#634)
7f91cef is described below

commit 7f91cef4048e3bbb2dd43cde6cf3bb69e2f806f8
Author: Otavio Rodolfo Piske <or...@users.noreply.github.com>
AuthorDate: Fri Sep 24 10:35:56 2021 +0200

    Fixed a small typo on the Camel Kafka blog post (#634)
---
 content/blog/2021/09/camel-kafka-consumer-changes/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2021/09/camel-kafka-consumer-changes/index.md b/content/blog/2021/09/camel-kafka-consumer-changes/index.md
index c4a2d39..a3c8323 100644
--- a/content/blog/2021/09/camel-kafka-consumer-changes/index.md
+++ b/content/blog/2021/09/camel-kafka-consumer-changes/index.md
@@ -52,7 +52,7 @@ The tests were run on an IBM 8335 GTH server with 2 Power 9 CPUs with 16 cores (
 
 We used Kafka's own producer performance test client to generate the load on the Kafka instance. On the consumer end, we implemented a simple mock consumer to compute the metrics and save the results. This mock consumer, with details about how to reproduce the test are also [available](https://github.com/orpiske/kafka-tester).
 
-The tests, which used the default configuration for the component, indicate that the performance of the component for highly concurrent scenarios was greater than 17% (sometimes far exceeding that) in our environment. For scenarios with low to none concurrency, the results were mostly within the 5% margin. Although Camel did perform better by a small percent on most of the time, at such a low difference it's certainly within the margin of error.
+The tests, which used the default configuration for the component, indicate that the performance of the component for highly concurrent scenarios was greater than 17% (sometimes far exceeding that) in our environment. For scenarios with low to none concurrency, the results were mostly within the 5% margin. Although the new component did perform better by a small percent on most of the time, at such a small difference it's certainly within the margin of error.
 
 
 ![Single consumer test](p9-single-consumers-default-settings.png)