Kaui: evaluate enabling JRuby invokedynamic (setenv.sh hard-codes -Djruby.compile.invokedynamic=false)
@tungleduyxyz is already working on this.
Since Nov 4, 2026.
Assessment
This issue has not been assessed yet.
Description
Summary
The shared Tomcat setenv.sh template turns JRuby's invokedynamic support off for every image built from it, Kaui included. A JRuby performance team recommends turning it on:
Method profiles end up being heavily polluted by non-indy method call logic, including some places that appear to be polymorphic and could benefit from the indy logic's polymorphic cache. [...] it will improve the quality of the profiles and it should perform better (if it does not then that's what we need to investigate, because it blows non-indy away on smaller stuff).
Where
ansible/templates/tomcat/conf/setenv.sh.j2#L35 (same line on master and java2x):
-Djruby.compile.invokedynamic=false
- The base image is shared by the Kill Bill and Kaui images. The setting was probably added for Kill Bill's JRuby plugins; it isn't documented why.
- It is present on the Java 21 / Tomcat 11 perf server, running Kill Bill 0.25.5 + Kaui 4.0.26 / JRuby 10.0.6.0 (checked on the running JVM's command line).
- Kaui can override it without touching Kill Bill:
ansible/templates/kaui/conf/setenv2.sh.j2appends{{ kaui_system_properties }}toCATALINA_OPTSaftersetenv.sh, and for a repeated-Dthe JVM uses the last value.
Relationship with the JIT login bug
The Kaui login bug (killbill/killbill-admin-ui-standalone#131) happens with invokedynamic on and off. It is a JIT bug in JRuby 10.0.x, fixed in 10.1.1.0+ (see killbill/killbill-admin-ui-standalone#133). So enabling indy is not blocked by it, as long as the current workaround (-Djruby.jit.exclude=Rails::Engine#call, killbill/killbill-cloud#346) or JRuby 10.1.1+ is in place.
Plan
- Experiment on the perf server, Kaui only: add
-Djruby.compile.invokedynamic=true(keeping thejit.excludeworkaround). - Run the same Gatling scenarios as the baseline (killbill-admin-ui-standalone
perf/, 10 users, 600 s), after warm-up: indy usually costs more at startup/warm-up and pays off once warm. Capture JFR for each run. - Compare with the baseline below. Check method profiles (less call-site overhead), allocation, p75/p95/p99, and warm-up time.
- If it's better, change the default for the Kaui image only (via
kaui_system_propertiesor the Kauisetenv2.sh.j2). Kill Bill's setting stays as is unless the Kill Bill team wants to evaluate it too.
Baseline (indy off, G1, shared Kill Bill + Kaui JVM on a t2.medium):
| Scenario | p75 | p95 | p99 |
|---|---|---|---|
| realistic mix | 1,097 ms | 1,978 ms | — |
account_show |
— | 331 ms | — |
timeline |
292 ms | 1,601 ms | 2,533 ms |
Acceptance criteria
- Before/after Gatling results and JFR recordings with indy on vs off (same instance, same data, after warm-up)
- Decision recorded; if positive, the Kaui image/role defaults to
-Djruby.compile.invokedynamic=true, and the reason for keeping (or changing) Kill Bill's setting is documented insetenv.sh.j2
Related
- killbill/killbill-admin-ui-standalone#131 / #133: JIT login bug and the JRuby 10.1 upgrade
- killbill/killbill-cloud#346: the
jit.excludeworkaround - killbill/killbill-cloud#344: Tomcat 11 / JDK 21
- killbill/killbill-client-ruby#125, #126 and killbill/killbill-admin-ui-standalone#136: the other items from the same profiling round
- Dominant language
- Ruby
- Stars
- 68
- Forks
- 93
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from killbill/killbill-cloud
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
killbill/killbill-cloud#265 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
killbill/killbill-cloud#351 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
killbill/killbill-cloud#302 ·
-
Support for Maven CentralMay be free again @tungleduyxyz claimed this 436 days ago, and no pull request is open. Open
killbill/killbill-cloud#291 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
killbill/killbill-cloud#283 · 1 comment ·
All issues in killbill/killbill-cloud
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
TheOdinProject/curriculum#31548 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
needs verification
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 13 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
palladius/rails8-app-on-gcp#244 ·
Maintainers usually reply within 1 day