fulmine.js: one entry, with the connection headers off - #1434
Merged
Conversation
…on the standard one
nigrosimone
marked this pull request as ready for review
September 3, 2026 17:25
nigrosimone
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
September 3, 2026 17:25
Contributor
Author
|
/benchmark --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Contributor
Author
|
👍 |
MDA2AV
approved these changes
Sep 3, 2026
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
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.
fulmine.js-tunedexisted to carry two things the standard entry could not: the file and stat caches, andConnection: keep-alive+Keep-Aliveleft off. The caches went in #1279, and the two headers are now what fulmine.js's own Performance tips recommend for an API behind a proxy or serving HTTP/1.1 clients (tip 10, released in 5.19.2) - the same footing the entry already stands on foretag. What is left between the two entries is one npm package on the two reference-only database profiles, which is not worth a second row on every board.So this removes
frameworks/fulmine-tunedand setsconnection headersto false on the standard entry's three apps. A request that asks forConnection: closeis still answeredConnection: closeand still closed; validation never looks at either header.Checked in Docker against the validation shapes: fragmented and lower-cased requests, chunked bodies,
/echofrom 1 B to 100 KB plus chunked and empty, json-comp still gzip with the right counts and totals, on 8080 and 8081.Two notes. The published
fulmine.jsrows were measured with the headers on, so they understate the entry until it is next benchmarked; no run is requested here. Andsite/leaderboard/data.jsis regenerated, which also picks up result rows that a few other entries landed without regenerating it.