Worker: use a different socket per run
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
To reduce load on pheonix, instead of all events going through a single socket, as now, we should create one socket per run.
On the pheonix side this means there's a process dedicated to each run, so processing of events will be much faster
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
Start by locating the worker's current shared socket and the code that defines a run's lifecycle. Trace how events are routed to Phoenix, then determine what must change so each run owns its socket and processing path; done means separate runs no longer share a socket and their events are processed independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100