Repository navigation
docs: the README and the published numbers, against v0.5.1 - #16
Merged
Merged
Conversation
The README said port 8686 binds to localhost. That is the bundled compose: the raw binary, which we publish, listens on 0.0.0.0:8686 with no token. Numbers measured on the v0.5.1 release binary: promote 20 ms over eight runs, graceful handoff at most 2 s and crash failover 4 to 5 s over four. "118 MB" did not reproduce: the image pulls 40.4 MB and unpacks to 100 MB. ~25x and ~70x still used the old RSS and binary; against 202 MB and 338 MB they are ~20x and ~30x. The kill -9 row quoted ~8 k/s: the run takes 31.5 s, on v0.3.6 as well, since what the dead instance held comes back after the 30 s ack wait. The README also gains what shipped since it was last read: mqtt-in/out, the standalone broker connectors, the file secret store, dead letters and governed mode, the prebuilt image and binary. ADRs keep the numbers of their day. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018wXgxT2UoFSZfqhAE1Tb5V
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.
Le README n'était plus à jour. Ce PR le corrige, avec les chiffres publiés ailleurs pour que les pages restent d'accord entre elles. Aucun code ne change.
Faux ou périmé
0.0.0.0:8686sans token.118 MBn'est pas reproductible. L'image pèse 40,4 Mo au téléchargement et 100 Mo déballée, d'après les couches du manifeste publié. Le118 MBvenait dedocker images, qui affiche 149 Mo aujourd'hui sur ce poste pour la même image.~25×et~70×reposaient sur les anciens RSS et binaire. Contre 202 Mo et 338 Mo, c'est~20×et~30×.Re-mesuré sur le binaire de la release v0.5.1
La ligne
kill -9citait~8 k/s. Le run dure 31,5 s, sur v0.3.6 comme sur v0.5.1, parce que ce que tenait l'instance tuée revient après l'ack wait de 30 s. Les 20 000 messages arrivent bien. Ce n'est pas une régression, et le tableau le dit maintenant.Ajouté au README
mqtt-in/mqtt-out, les connecteurs de brokers autonomes, le magasin de secrets fichier et le placeholder dans tout ce qui montre un run, les dead letters, le mode gouverné, l'image et le binaire précompilés.Pas touché
Les ADR gardent les chiffres de leur époque.
Après le merge
scripts/deploy-docs.sh masteretscripts/deploy-site.sh, puisque le book etsite/index.htmlchangent.🤖 Generated with Claude Code
https://claude.ai/code/session_018wXgxT2UoFSZfqhAE1Tb5V