[SERVER-82501] Add operation BadnessPolicy Created: 27/Oct/23 Updated: 28/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Yujin Kang Park | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
Provides a ‘badness’ score for a given operation. Borrowing the ‘badness’ term from the kernel’s OOM killer, this score indicates how suitable an operation is for being shed. We should introduce a single default implementation, which will use an estimation of memory usage. The higher the estimated memory usage of the operation, the higher its badness score. |