fix: reduce shadow wstunnel memory usage#542
Draft
Sam6734 wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Sam <55770131+Sam6734@users.noreply.github.com>
✅ Deploy Preview for interlink-dev canceled.
|
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.
Each FullMesh shadow pod runs its own wstunnel server. Wstunnel defaults its Tokio worker-thread count to the number of CPUs visible on the Kubernetes node, so the small per-worker tunnel process created many unnecessary threads and consumed about 480 MiB on our cluster
Set
TOKIO_WORKER_THREADS=1for the wstunnel container because each deployment handles one worker tunnel.Performed Isolated test using the same
ghcr.io/erebe/wstunnel:latestimage with one Tokio thread: 11 MiB