Conversation
agentgt
force-pushed
the
feature/webapp-benchmark
branch
5 times, most recently
from
August 26, 2026 00:49
abaa348 to
5fc5a08
Compare
agentgt
marked this pull request as draft
August 26, 2026 09:46
agentgt
force-pushed
the
feature/webapp-benchmark
branch
3 times, most recently
from
August 26, 2026 20:11
ad5c31f to
05f4506
Compare
agentgt
force-pushed
the
feature/webapp-benchmark
branch
2 times, most recently
from
September 4, 2026 12:52
d9e145a to
0abd0a9
Compare
… vs RainbowGum)
Squashed history of the webapp benchmark investigation (previously developed
on webapp-benchmark-0-10-0, pinned to the v0.10.0 release point) onto current
main. Adds a real Spring Boot 4 webapp per framework (rainbowgum-benchmark-
webapp-{logback,log4j2,rainbowgum}), a load-testing driver module, and three
run scripts covering the full scenario matrix:
- run-all.sh: default/GELF/virtual-threads/GELF+VT, always console+file
- run-k8s.sh: GELF to console only (no file) - the 12-factor/k8s deployment
shape - both platform and virtual threads, all three frameworks
- run-tomcat-jul.sh: isolates an unexplained ~15-17% throughput regression
from the rainbowgum-tomcat JUL bridge
See FINDINGS.md for the durable why (Logback vs Log4j2/RainbowGum tradeoffs
under virtual vs platform threads, the String.getBytes() Latin1 fast path,
LOCK_THREAD_LOCAL_BUFFER vs SYNCHRONIZED_THREAD_LOCAL_BUFFER under VT) and
RESULTS.md for the latest numbers - RainbowGum wins 5 of 6 scenarios, with
the k8s/console-only scenario its best result (~1.8-2x both competitors).
Also moves the original hand-rolled micro-benchmarks (tight-loop calls, no
HTTP layer) under benchmark/legacy, isolated there so their logback-classic/
log4j-slf4j2-impl dependencyManagement pins can never again leak into and
override a Spring Boot BOM the way they once did when both lived as siblings
directly under benchmark/pom.xml.
Full reactor build and tests pass clean.
agentgt
force-pushed
the
feature/webapp-benchmark
branch
from
September 11, 2026 20:10
0abd0a9 to
4f935aa
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.