This is an automated email from the ASF dual-hosted git repository.
wilfreds pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git
The following commit(s) were added to refs/heads/master by this push:
new c4fbb6934c [YUNIKORN-2224] add preemption to core feature (#375)
c4fbb6934c is described below
commit c4fbb6934cf36636006c5abcb42ac52eb65df617
Author: DouPache <[email protected]>
AuthorDate: Thu Jan 25 16:12:29 2024 +1100
[YUNIKORN-2224] add preemption to core feature (#375)
Closes: #375
Signed-off-by: Wilfred Spiegelenburg <[email protected]>
---
docs/get_started/core_features.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/docs/get_started/core_features.md
b/docs/get_started/core_features.md
index 8c9076fe50..ddb3039219 100644
--- a/docs/get_started/core_features.md
+++ b/docs/get_started/core_features.md
@@ -74,6 +74,9 @@ This mechanism can avoid this pod gets starved by later
submitted smaller, less-
This feature is important in the batch workloads scenario because when a large
amount of heterogeneous pods is submitted
to the cluster, it's very likely some pods can be starved even they are
submitted much earlier.
+## Preemption
+YuniKorn's preemption feature allows higher-priority tasks to dynamically
reallocate resources by preempting lower-priority ones, ensuring critical
workloads get necessary resources in a multi-tenant Kubernetes environment.
This proactive mechanism maintains system stability and fairness, integrating
with Kubernetes' priority classes and YuniKorn's hierarchical queue system.
+
## Throughput
Throughput is a key criterion to measure scheduler performance. It is critical
for a large scale distributed system.
If throughput is bad, applications may waste time on waiting for scheduling,
and further impact service SLAs.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
