vhive-serverless / vhive-serverless/invitro
Spillover tracking
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 29
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
We have decided to turn off this feature until we determine the fate of it.
Failure rate tracking should not be done per minute, but per experiment, since for functions with a small number of invocations it can happen that a relative difference becomes too large, which implies per-function driver termination.
It could lead to non-deterministic experiments in the presence of failures.
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 file, test, or entry point is named. First locate the spillover and failure-rate tracking implementation, then review the project’s experiment-related tests and clarify whether tracking should be disabled or measured per experiment before defining what done means.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100