Skip to content

Commit b2791f3

Browse files
committed
Change caption to alt in figure
1 parent bd951ea commit b2791f3

File tree

1 file changed

+2
-2
lines changed
  • content/en/blog/_posts/2024-08-22-cpumanager-static-policy-distributed-cpu-across-cores

1 file changed

+2
-2
lines changed

content/en/blog/_posts/2024-08-22-cpumanager-static-policy-distributed-cpu-across-cores/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ In Kubernetes v1.31, we are excited to introduce a significant enhancement to CP
1414

1515
Traditionally, Kubernetes' CPUManager tends to allocate CPUs as compactly as possible, typically packing them onto the fewest number of physical cores. However, allocation strategy matters, CPUs on the same physical host still share some resources of the physical core, such as the cache and execution units, etc.
1616

17-
{{< figure src="cpu-cache-architecture.png" caption="cpu-cache-architecture" >}}
17+
{{< figure src="cpu-cache-architecture.png" alt="cpu-cache-architecture" >}}
1818

1919
While default approach minimizes inter-core communication and can be beneficial under certain scenarios, it also poses a challenge. CPUs sharing a physical core can lead to resource contention, which in turn may cause performance bottlenecks, particularly noticeable in CPU-intensive applications.
2020

@@ -23,7 +23,7 @@ The new `distribute-cpus-across-cores` feature addresses this issue by modifying
2323

2424
Technically, within this static policy, the free CPU list is reordered in the manner depicted in the diagram, aiming to allocate CPUs from separate physical cores.
2525

26-
{{< figure src="cpu-ordering.png" caption="cpu-ordering" >}}
26+
{{< figure src="cpu-ordering.png" alt="cpu-ordering" >}}
2727

2828

2929
## Enabling the feature

0 commit comments

Comments
 (0)