allthingssecurity opened a new pull request, #162:
URL: https://github.com/apache/camel-performance-tests/pull/162

   A JMH benchmark of the exchange sanitizer (camel-sanitizer) and the table of 
pending calls of its rule R1 "still pending", as the Validation section of 
`design/exchange-sanitizer.adoc` asks. The change itself is apache/camel#29528 
([CAMEL-26751](https://issues.apache.org/jira/browse/CAMEL-26751)).
   
   What `SanitizerPendingTest` (camel-jmh) measures, in ns per message:
   - `mode`: `off` (camel-sanitizer on the classpath, `enabled=false`), `t0` 
(`pendingTimeout=0`, no table) and `t60` (`pendingTimeout=60s`, with the table, 
the exchange-done notifier and the checker thread);
   - `stackDepth`: 0 and 32;
   - routes: `steps` (6 steps), `split` (a split of 4, then a seda send), and 
`psplit4`/`psplit8` (a parallel split of 16 parts on a pool of 4 or 8 threads);
   - `send_1` and `send_4`: 1 and 4 producer threads on one shared context.
   
   How to run:
   
   ```bash
   mvn test -P jmh,sanitizer -Dcamel.version=4.24.0-SNAPSHOT 
-Dtest=SanitizerPendingTest -DargLine="-Xms1g -Xmx1g"
   ```
   
   camel-sanitizer is in a new profile, `sanitizer`. Without that profile the 
benchmark is skipped, so the module builds as before with the default 
`camel.version`.
   
   Draft until apache/camel#29528 is merged and a 4.24.0-SNAPSHOT with the 
`pendingTimeout` option is published. I compiled the class with javac against 
the jars of that PR's branch, with and without camel-sanitizer, and ran it 
there. I did not run the Maven build of this repository: offline, the 
4.24.0-SNAPSHOT BOM is not available.
   
   _Claude Code on behalf of allthingssecurity_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to