Claus Ibsen created CAMEL-26994:
-----------------------------------

             Summary: camel-jbang - run the short commands of the CLI with C1 
only, and do not pass it on to the integrations
                 Key: CAMEL-26994
                 URL: https://issues.apache.org/jira/browse/CAMEL-26994
             Project: Camel
          Issue Type: Improvement
          Components: camel-jbang
            Reporter: Claus Ibsen
             Fix For: 4.25.0


Split out of CAMEL-26937 (item 3), moved to 4.25.0 (Claus, 2026-11-15): it 
changes camel.sh and camel.bat, as the JDK 25 AOT cache of CAMEL-26940 does, 
which is too close to the 4.24.0 release.

h3. What

Run the JVM of the short CLI commands (ps, get, doc, log, cmd ..., version, 
validate) with {{-XX:TieredStopAtLevel=1}} (C1 only). Measured on 2026-11-13 
(JDK 25, warm CDS): get route 0.287 -> 0.241 s, validate 0.420 -> 0.349 s, and 
half the user CPU. Measured again on 2026-11-15 on top of the CLI SLF4J 
provider of CAMEL-26937 (PR https://github.com/apache/camel/pull/30016): ps 140 
-> 127 ms, get route 170 -> 162 ms, camel log 347 -> 327 ms.

h3. What to watch

* Per command, in camel.sh and camel.bat: a foreground {{camel run}} (and dev, 
debug, the TUI, the shell, the MCP server, infra run, export) runs the 
integration or long work in the CLI JVM and must keep C2. The scripts already 
pick a CDS archive per command name, which is where to choose.
* It must not reach the integrations: {{LauncherHelper.getCamelCommand()}} 
forwards every -D/-X argument of the CLI JVM to a background integration (which 
today also caps integrations at -Xmx512m). Filter -XX:TieredStopAtLevel there.
* Fall back to the default when JAVA_OPTS already sets a JIT option.

Related: CAMEL-26937 (startup), CAMEL-26940 (AOT cache, 4.25.0), CAMEL-26961 
(resident daemon, 4.25.0).

_Claude Code on behalf of Claus Ibsen (davsclaus)_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to