Merge pull request #48674 from my-git9/pp-17464

[zh-cn]sync manage-resources-containers.md
This commit is contained in:
Kubernetes Prow Robot 2024-11-11 00:16:44 +00:00 committed by GitHub
commit a927502302
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 9 deletions

View File

@ -350,7 +350,7 @@ limits you defined.
{{< glossary_tooltip text="CGroups" term_id="cgroup" >}},负责应用并实施所定义的请求。 {{< glossary_tooltip text="CGroups" term_id="cgroup" >}},负责应用并实施所定义的请求。
<!-- <!--
- The CPU limit defines a hard ceiling on how much CPU time that the container can use. - The CPU limit defines a hard ceiling on how much CPU time the container can use.
During each scheduling interval (time slice), the Linux kernel checks to see if this During each scheduling interval (time slice), the Linux kernel checks to see if this
limit is exceeded; if so, the kernel waits before allowing that cgroup to resume execution. limit is exceeded; if so, the kernel waits before allowing that cgroup to resume execution.
--> -->
@ -463,8 +463,8 @@ Kubernetes 基于资源请求(`Pod.spec.containers[].resources.requests`)调
<!-- <!--
From the perspective of memory management, there are some similarities between From the perspective of memory management, there are some similarities between
when a process uses memory as a work area and when using memory-backed when a process uses memory as a work area and when using memory-backed
`emptyDir`. But when using memory as a volume like memory-backed `emptyDir`, `emptyDir`. But when using memory as a volume, like memory-backed `emptyDir`,
there are additional points below that you should be careful of. there are additional points below that you should be careful of:
--> -->
从内存管理的角度来看,进程使用内存作为工作区与使用内存作为 `emptyDir` 的介质有一些相似之处。 从内存管理的角度来看,进程使用内存作为工作区与使用内存作为 `emptyDir` 的介质有一些相似之处。
但当将内存用作存储卷(例如内存为介质的 `emptyDir` 卷)时,你需要额外注意以下几点: 但当将内存用作存储卷(例如内存为介质的 `emptyDir` 卷)时,你需要额外注意以下几点: