MemoryWatermark tune operation interferes all apps.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
What happened:
Sandbox not full isolated.
What you expected to happen:
If app A cost massive memory which result in availble memory less than Critical MemoryWatermark, then the runtime will tune smr param: "MAX_WORKERS_PER_APP", that's now the logic. But the tune operation will scale in the running app B , the scale in operation is triggered by app A.
That sound like not a good isolation behavior, apps interfere each other.
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 tracing the runtime's MemoryWatermark handling and the MAX_WORKERS_PER_APP tuning path. Reproduce the scenario with app A consuming enough memory to cross Critical MemoryWatermark while app B is running. Done means memory pressure from app A no longer scales in app B, preserving isolation between apps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100