[CAMEL-19058] Type check scalability issue

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0-RC1, 4.0.0
• Component/s: camel-core, camel-disruptor, camel-seda
• Estimated Complexity: Unknown
• Assignee: Otavio Rodolfo Piske
• Reporter: Otavio Rodolfo Piske
• Created: 16/Feb/23 06:13
• Updated: 21/Mar/24 12:45
• Resolved: 17/Jul/23 09:22

Description

Camel 3.x as well as 4.0.0-M1 reportedly have multiple cases of the type-check scalability described in this post. 

This can affect the the scalability of Camel when running with multiple threads and incur in extra unnecessary work.

See the attachment sample-trace-for-m1.txt for a report of the possible cases for M1 (triggered by running a simple application using seda).

The initial set of patches for CAMEL-15105 have helped a great deal to remove these, but there's still a few to resolve.

 

 

Issue Links

• incorporates: CAMEL-15105 camel-core - Extension or getter/setter on ExtendedCamelContext
• incorporates: CAMEL-19102 camel-core: Producer cache offers poor performance due to the type check scalability issue
• relates to: CAMEL-19775 camel-main: main duration event is not enabled for exchange completed
• relates to: CAMEL-19781 camel-core: excessive occurrence of type misses may be hurting performance
• links to: GitHub Pull Request #9432
• links to: GitHub Pull Request #9450
• links to: GitHub Pull Request #9968
• links to: GitHub Pull Request #9982
• links to: GitHub Pull Request #9984
• links to: GitHub Pull Request #9986