Values of Dynamic Parameters in Different Runtime Environments

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 不同运行环境下动态参数的值

| username: liyuntang

[TiDB Usage Environment] Production Environment
[TiDB Version] v7.1.0
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

The values of high-concurrency, normal-concurrency, and low-concurrency parameters are dynamic (changing with the number of CPU cores). If TiDB is deployed in a k8s environment, does the number of CPU cores here refer to the physical machine’s CPU cores or the CPU resources allocated to the pod?

| username: tidb菜鸟一只 | Original post link

It seems that tidb-k8s has not obtained the CPU resources of a single pod, but rather the entire physical machine’s.

| username: TiDBer_QYr0vohO | Original post link

Inside the pod container, the CPU and memory resources are those of the physical machine where the pod is located. It seems that the physical machine’s CPU is used for computation.

| username: xiaoqiao | Original post link

K8 is generally suitable for stateless services and not suitable for databases; storage cannot be switched.

| username: liyuntang | Original post link

After verification, all are physical machine resources and have nothing to do with the pod.

| username: QH琉璃 | Original post link

Haven’t used it.

| username: TiDBer_JUi6UvZm | Original post link

Following, haven’t used it.

| username: 呢莫不爱吃鱼 | Original post link

Here to learn and build up some knowledge.