Skip to content

Commit 4d7f4f5

Browse files
Jeffwanklueska
andauthored
Update keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy/README.md
Co-authored-by: Kevin Klues <[email protected]>
1 parent f3c867a commit 4d7f4f5

File tree

1 file changed

+1
-1
lines changed
  • keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy

1 file changed

+1
-1
lines changed

keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -221,7 +221,7 @@ bogged down.
221221

222222
#### Story 1 Bytedance Database Performance Optimization
223223

224-
We're running DB instances in Kubernetes and adopt default static policy in the past. While, we notice that the performance of DB instances is not stable. If an instance is under pressure, in original way, it was allocated two cpus from same physical core. However, an important pattern we notice is not always all instances are busy. After exploration, we find that the CPU cache is one bottleneck, once we spread hyper threads across physical cores, the busy instance can leverage more CPU cache and performance is improved a lot.
224+
We're running DB instances in Kubernetes and adopt default static policy in the past. While, we notice that the performance of DB instances is not stable. If an instance is under pressure, in original way, it was allocated two CPUs from same physical core. However, an important pattern we notice is not always all instances are busy. After exploration, we find that the CPU cache is one bottleneck, once we allocate CPUs across physical cores, the busy instance can leverage more CPU cache and performance is improved a lot.
225225

226226
#### Story 2
227227

0 commit comments

Comments
 (0)