Add Rails comparison: Action Cable / Solid Cable / AsyncCable / AnyCable#2
Open
irinanazarova wants to merge 1 commit into
Open
Add Rails comparison: Action Cable / Solid Cable / AsyncCable / AnyCable#2irinanazarova wants to merge 1 commit into
irinanazarova wants to merge 1 commit into
Conversation
Target apps and harness for the Rails WebSocket adapter comparison behind
anycable.io/compare/rails-actioncable.
Targets:
- cable-bench/ Rails 8.1 app, BENCH_MODE selects Action Cable (Redis)
or Solid Cable (database); also the AnyCable RPC backend
- cable-bench-falcon/ same app booted on Falcon via actioncable-next +
async-cable (the AsyncCable target)
Harness:
- idle-multi.ts: forward CHANNEL/AC_PROTOCOL and send the bench-runner auth
token, so idle/capacity runs can target a real Rails channel
- jitter-multi.ts: forward CHANNEL + AC_PROTOCOL for Rails targets
- idle-runner.ts / jitter-runners.ts / server.ts: channel + acProtocol params
- tests-manifest.ts: Rails latency/jitter/idle/avalanche/capacity specs
Results (sharded, one shared-tenant Railway window):
- backend/results/rails-sharded-2026-06-28.json latency/jitter/10K/idle/avalanche
- backend/results/rails-capacity-break-2026-06-28.json idle-to-break per adapter
Deep dive in docs/rails-comparison.md; summary in README.
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.
Target apps, harness changes, and results for the Rails WebSocket adapter comparison behind anycable.io/compare/rails-actioncable.
Target apps
cable-bench/— Rails 8.1 app;BENCH_MODEselects Action Cable (Redis) or Solid Cable (database). Also serves as the AnyCable gRPC RPC backend.cable-bench-falcon/— the same app booted on Falcon viaactioncable-next+async-cable(the AsyncCable target).Harness
idle-multi.ts: forwardCHANNEL/AC_PROTOCOLand send the bench-runner auth token, so idle/capacity runs can target a real Rails channeljitter-multi.ts: forwardCHANNEL+AC_PROTOCOLfor Rails targetsidle-runner.ts/jitter-runners.ts/server.ts:channel+acProtocolparamstests-manifest.ts: Rails latency/jitter/idle/avalanche/capacity specsResults (sharded, one shared-tenant Railway window)
backend/results/rails-sharded-2026-06-28.json— latency, jitter, 10K, idle, avalanchebackend/results/rails-capacity-break-2026-06-28.json— idle-to-break per adapter (AnyCable held 600K with 0 failures)Deep dive in
docs/rails-comparison.md; summary section inREADME.md.