Tunnel Performance Parameters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Chisel is currently running on my EKS cluster as a pod, and I would like to perform a stress test & create observability for it.
What i'm not sure of is the parameters to look for on that test.
In other words, how can I know if my tunnel is well-functioned and I can add more clients to it, or its already on its limit and I need to take actions accordingly.
Im already testing if I have a connection on my tunnel, but I yet to determine the quality of it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified; first define the stress-test parameters and observability signals for a Chisel tunnel running as an EKS pod. Done should be a documented way to assess tunnel quality and capacity for additional clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, networking, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100