This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/master by this push:
new 2f4760f Whats new in Camel 3.6. (#489)
2f4760f is described below
commit 2f4760f3ea07e1bcd0a942f10ddfa3f473b82898
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Tue Oct 20 22:03:37 2020 +0200
Whats new in Camel 3.6. (#489)
Whats new in Camel 3.6.
---
.../2020/10/Camel36-Whatsnew/350-allocations.png | Bin 0 -> 131582 bytes
.../blog/2020/10/Camel36-Whatsnew/350-blocked.png | Bin 0 -> 406567 bytes
.../2020/10/Camel36-Whatsnew/350-performance.png | Bin 0 -> 322052 bytes
.../2020/10/Camel36-Whatsnew/360-allocations.png | Bin 0 -> 144661 bytes
.../blog/2020/10/Camel36-Whatsnew/360-blocked.png | Bin 0 -> 316712 bytes
.../2020/10/Camel36-Whatsnew/360-performance.png | Bin 0 -> 90306 bytes
content/blog/2020/10/Camel36-Whatsnew/featured.png | Bin 0 -> 3975989 bytes
content/blog/2020/10/Camel36-Whatsnew/index.md | 135 +++++++++++++++++++++
8 files changed, 135 insertions(+)
diff --git a/content/blog/2020/10/Camel36-Whatsnew/350-allocations.png
b/content/blog/2020/10/Camel36-Whatsnew/350-allocations.png
new file mode 100644
index 0000000..aac809c
Binary files /dev/null and
b/content/blog/2020/10/Camel36-Whatsnew/350-allocations.png differ
diff --git a/content/blog/2020/10/Camel36-Whatsnew/350-blocked.png
b/content/blog/2020/10/Camel36-Whatsnew/350-blocked.png
new file mode 100644
index 0000000..9e377db
Binary files /dev/null and
b/content/blog/2020/10/Camel36-Whatsnew/350-blocked.png differ
diff --git a/content/blog/2020/10/Camel36-Whatsnew/350-performance.png
b/content/blog/2020/10/Camel36-Whatsnew/350-performance.png
new file mode 100644
index 0000000..ecd7f93
Binary files /dev/null and
b/content/blog/2020/10/Camel36-Whatsnew/350-performance.png differ
diff --git a/content/blog/2020/10/Camel36-Whatsnew/360-allocations.png
b/content/blog/2020/10/Camel36-Whatsnew/360-allocations.png
new file mode 100644
index 0000000..d040505
Binary files /dev/null and
b/content/blog/2020/10/Camel36-Whatsnew/360-allocations.png differ
diff --git a/content/blog/2020/10/Camel36-Whatsnew/360-blocked.png
b/content/blog/2020/10/Camel36-Whatsnew/360-blocked.png
new file mode 100644
index 0000000..561c006
Binary files /dev/null and
b/content/blog/2020/10/Camel36-Whatsnew/360-blocked.png differ
diff --git a/content/blog/2020/10/Camel36-Whatsnew/360-performance.png
b/content/blog/2020/10/Camel36-Whatsnew/360-performance.png
new file mode 100644
index 0000000..39b4d85
Binary files /dev/null and
b/content/blog/2020/10/Camel36-Whatsnew/360-performance.png differ
diff --git a/content/blog/2020/10/Camel36-Whatsnew/featured.png
b/content/blog/2020/10/Camel36-Whatsnew/featured.png
new file mode 100644
index 0000000..e5077f5
Binary files /dev/null and b/content/blog/2020/10/Camel36-Whatsnew/featured.png
differ
diff --git a/content/blog/2020/10/Camel36-Whatsnew/index.md
b/content/blog/2020/10/Camel36-Whatsnew/index.md
new file mode 100644
index 0000000..20a1cae
--- /dev/null
+++ b/content/blog/2020/10/Camel36-Whatsnew/index.md
@@ -0,0 +1,135 @@
+---
+title: "Apache Camel 3.6 What's New"
+date: 2020-10-21
+authors: [davsclaus]
+categories: ["Releases"]
+preview: Details of what we have done in the Camel 3.6 release.
+---
+
+Apache Camel 3.6 has just been released.
+
+This is a non-LTS release which means we will not provide patch releases but
use the release _as-is_.
+The next planned LTS release is 3.7 scheduled towards the end of the year.
+
+
+## So what's in this release?
+
+This release introduces a set of new features and noticeable improvements that
we will cover in this blog post.
+
+
+### Spring Boot
+
+We have upgraded to the latest release at this time which is Spring Boot 2.3.4.
+Support for Spring Boot 2.4 is planned for Camel 3.7.
+
+
+### Optimizations
+
+To speed up the startup we switched to a new UUID generator. The old (classic)
generator was inherited from Apache ActiveMQ which needed to ensure its ids
were unique in a network of brokers, and therefore to ensure this the generator
was using the hostname as the prefix in the id. This required on startup to do
network access to obtain this information which costs a little time. Also
depending on networks this can be more restrictive and delay the startup. The
new generator is a pure in [...]
+
+We also identified a few other spots during route initialization. For example,
one small change was to avoid doing some regular expression masking on route
endpoints which weren't necessary anymore.
+
+Now the bigger improvements are in the following areas
+
+#### Avoid throwing exceptions
+
+We identified on spring runtimes that Camel would query the spring bean
registry for known beans by id, which the Spring framework would throw a
NoSuchBeanDefinitionException if the bean is not present. As Camel does a bit
of optional bean discovery during bootstrap, we found a way to avoid this which
prevents this.
+
+#### Singleton languages
+
+Another related problem is that in Camel 3 due to the modularization then some
of the languages (bean, simple, and others) have been changed from being a
singleton to prototype scoped. This is one of the biggest problems and we had a
Camel user report a problem with thread contention in a high concurrent
use-case would race for resolving languages (they are prototype scoped). So you
would have this problem, and because the language resolver would query the
registry first then Spring woul [...]
+
+{{< image "350-blocked.png" "Camel 3.5 Blocked Threads" >}}
+
+{{< image "360-blocked.png" "Camel 3.6 Blocked Threads" >}}
+
+The top screenshot is using Camel 3.5 and the bottom 3.6. At the top, we can
see the threads are blocked in Camel's `resolveLanguage` method. And in 3.6
then it's the log4j logger that is blocking for writing to the log file. Both
applications are using the same Camel application and have been running for
about 8 minutes.
+
+#### Reduce object allocations
+
+The next screenshots are showing a sample of the object allocations.
+
+{{< image "350-allocations.png" "Camel 3.5 Average Object Allocations Per
Seconds" >}}
+
+{{< image "360-allocations.png" "Camel 3.6 Average Object Allocations Per
Seconds" >}}
+
+
+With Camel 3.5 we are average about 1000 obj/sec and with 3.6 we are down to
about a 1/3th.
+
+One of the improvements to help reduce the object allocations was how
parameters to languages was changed from using a Map to a plain object array.
The Map takes up more memory and object allocations than a single fixed object
array.
+
+#### Do as much init as possible
+
+Another performance improvement that aids during runtime was that we moved as
much we could from the evaluation to the initialization phase in the Camel
languages (simple, bean, etc.). We did this by introducing the init phase and
ensuring CamelContext was carried around in the interns so we can use the
context during the init phase, where its really needed. This ensures the
runtime evaluation is as fast as possible.
+
+#### Other smaller optimizations
+
+We also improved the simple language to be a bit smarter in its binary
operators (such as header.foo > 100). Now the simple language has stronger
types for numeric and boolean types during its parsing, which allows us to know
better from the right and left hand side of the binary operator to do type
coercion so the types are comparable by the JVM. Before we may end up with
falling back to converting to string types on both sides. And there is more to
come, I have some ideas how to work o [...]
+
+The screenshots below show a chart with the CPU, object allocations, and
thrown exceptions.
+
+{{< image "350-performance.png" "Camel 3.5 Performance Charts" >}}
+
+{{< image "360-performance.png" "Camel 3.6 Performance Charts" >}}
+
+
+As we can see this summarise what was mentioned was done to optimize. The
number of exceptions has been reduced to 0 at runtime. There is about 3500
thrown during bootstrap (that is Java JAXB which is used for loading the spring
XML file with the Camel routes used for the sample application). We do have a
fast XML loader in Camel that is not using JAXB.
+
+Another improvement we did was to build a source code generator for a new
`UriFactory` which allows each component to quickly build dynamic endpoint URIs
from a `Map` of parameters. The previous solution was to use
`RuntimeCamelCatalog` that was more generic and required loading component
metadata from JSON descriptor files. A few components use this to optimize the
`toD` (such as HTTP components). By this change, we avoid the runtime catalog
as a dependency (reduce JAR size) and the sou [...]
+
+Source from [external blog
post](http://www.davsclaus.com/2020/10/apache-camel-36-more-camel-core.html)
+
+
+### API Components overhaul
+
+There are several API based components which are source code generated from
_external API_. We have overhauled the code generator which now scrapes and
includes documentation and keep the documentation up to date as well.
+
+Also, we include additional metadata for Camel tooling so they can provide
code assistance when Camel end-users are using these API based components. Some
of those external APIs are huge and you can have hundreds of APIs.
+
+The API based components are:
[AS2](https://camel.apache.org/components/latest/as2-component.html),
[Box](https://camel.apache.org/components/latest/box-component.html),
[Braintree](https://camel.apache.org/components/latest/braintree-component.html),
[FHIR](https://camel.apache.org/components/latest/fhir-component.html), Google
[Calendar](https://camel.apache.org/components/latest/google-calendar-component.html)/[Drive](https://camel.apache.org/components/latest/google-drive-component.h
[...]
+
+
+### Reduce reflection
+
+Yet another release where we reduced using reflections in a few spots in Camel
core and in some of the components.
+
+
+### Language precompilation
+
+As mentioned in the optimization section we moved initialization of languages
to an earlier phase.
+Camel now pre compile languages when its applicable, for example JSonPath, and
XPath language.
+
+And speaking of pre-compiled languages then Camel 3.7 introduces the [jOOR
language](https://camel.apache.org/components/latest/languages/joor-language.html)
+to use runtime compile Java in the Camel DSL. A compiled simple language is
also on the roadmap.
+
+
+### Optimized components startup
+
+The camel core has been optimized in Camel 3 to be small, slim, and fast on
startup. This benefits Camel Quarkus which
+can do built time optimizations that take advantage of the optimized camel
core.
+
+We have continued this effort in the Camel components where whenever possible
initialization is moved ahead
+to an earlier phase during startup, that allows enhanced built time
optimizations. As there are a lot of Camel
+components then this work will progress over the next couple of Camel releases.
+
+
+### New components
+
+This was a historical slow release in terms of new components. In fact there
is only 1 new component:
+
+- AWS2-EventBridge: Manage AWS EventBridge cluster instances
+
+You can read more about the new AWS EventBridge component
+in the [blog
announcement](https://camel.apache.org/blog/2020/10/camel-aws2-eventbridge-intro/).
+
+
+## Upgrading
+
+Make sure to read the [upgrade
guide](https://camel.apache.org/manual/latest/camel-3x-upgrade-guide-3_6.html)
if you
+are upgrading to this release from a previous Camel version.
+
+
+## Release Notes
+
+You can find more information about this release in the [release
notes](https://camel.apache.org/releases/release-3.6.0/),
+with a list of JIRA tickets resolved in the release.
