ultimate-express: json-tls, static-tls, crud and fortunes - #1246
Open
MDA2AV wants to merge 2 commits into
Open
Conversation
The four HTTP/1.1 profiles the entry was not subscribed to. json-tls and static-tls listen on 8081. ultimate-express takes TLS material through the uWS options at construction rather than through a separate https server, so the port is a second express() carrying the same routes - the route table moved into registerRoutes() and both apps are built from it. Every worker in the cluster binds 8081 the same way they all bind 8080, so the listener is spread rather than parked on one process; measured at 32/32 workers burning CPU on both ports, 618k rps over TLS against 751k plaintext for /json/50. crud runs cache-aside on Redis through ioredis, one connection per worker so the cache is shared across the cluster, with a 200ms TTL and an explicit delete on update. express.json() is mounted on the two crud routes that carry a body rather than globally, so /upload keeps counting its 20MB body as it streams instead of having it buffered and parsed. fortunes is emitted by hand rather than through a template engine, which tuned mode allows. The handler still queries per request, appends the runtime row, sorts ordinally and escapes < > & " ' - the seed's row 11 carries a <script> tag and the profile's load-bearing check is that it leaves as text. Validation: 64 passed, 0 failed.
MDA2AV
force-pushed
the
feat/ultimate-express-missing-profiles
branch
from
August 21, 2026 22:35
ddef876 to
7742545
Compare
Owner
Author
|
/benchmark --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
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.
The four HTTP/1.1 profiles the entry was not subscribed to. Tests go from 10 to 14.
json-tls / static-tls
ultimate-express takes TLS material through the uWS options at construction
rather than through a separate
httpsserver, so 8081 is a secondexpress()carrying the same routes. The route table moved into
registerRoutes()and bothapps are built from it — no second copy of the handlers.
After #1245 I checked this the same way rather than trusting validation, which is
correctness-only and cannot see a listener pinned to one process. Every worker in
the cluster binds 8081 exactly as they all bind 8080:
/json/50, c=256)static-tlswith the profile's ownstatic-rotate.luadoes 235318 rps.crud
Cache-aside on Redis through
ioredis, one connection per worker so the cache isshared across the cluster rather than being a per-worker map, 200ms TTL, explicit
delete on update.
express.json()is mounted on the two crud routes that carry abody rather than globally —
/uploadtakes a 20MB body it counts as it streams,and a global parser would buffer and parse it.
fortunes
Emitted by hand rather than through a template engine, which tuned mode
explicitly allows. The handler still queries per request, appends the runtime
row, sorts ordinally and escapes
<>&"'— the seed's row 11 carriesa
<script>tag and the profile's load-bearing check is that it leaves as text.The existing static handler already read bodies from disk on every request, so it
needed no change to take
static-tls.Validation
64 passed, 0 failed, including all four new profiles:
🤖 Generated with Claude Code