Add cpuset pinning and dynamic WG bucket count#1
Draft
amiller wants to merge 1 commit intotokscope-xordi-perffrom
Draft
Add cpuset pinning and dynamic WG bucket count#1amiller wants to merge 1 commit intotokscope-xordi-perffrom
amiller wants to merge 1 commit intotokscope-xordi-perffrom
Conversation
- BROWSER_CPUSET_CPUS env var for CPU pinning during profiling - WIREGUARD_BUCKET_COUNT env var (was hardcoded to 10) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
These are two changes we made during staging that don't hurt.
The CPUSET CPUs is useful for limiting the total amount of CPUs, which is useful for bnechamrking on the staging server but not relevant for prod anyway. So it's instrumentation
The wireguard buckets were hardcoded previously, it's easier not to have to need all 10