From e9310044ce378f8df107cd7039cef97794dfc53e Mon Sep 17 00:00:00 2001 From: Derek Su Date: Tue, 20 Jun 2023 13:37:19 +0800 Subject: [PATCH] Highlight CPU usage in v2-data-engine setting Longhorn 6126 Signed-off-by: Derek Su (cherry picked from commit 46e1bb2cc339082c0bbc9170e44085f7d528ca7f) --- chart/questions.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chart/questions.yaml b/chart/questions.yaml index 5152209..ca40a74 100644 --- a/chart/questions.yaml +++ b/chart/questions.yaml @@ -689,9 +689,9 @@ Set the value to **0** to disable backup restore." label: V2 Data Engine description: "This allows users to activate v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. WARNING: - - The cluster must have pre-existing Multus installed, and NetworkAttachmentDefinition IPs are reachable between nodes. - DO NOT CHANGE THIS SETTING WITH ATTACHED VOLUMES. Longhorn will block this setting update when there are attached volumes. - - When applying the setting, Longhorn will restart all instance-manager pods." + - When applying the setting, Longhorn will restart all instance-manager pods. + - When the V2 Data Engine is enabled, each instance-manager pod utilizes 1 CPU core. This high CPU usage is attributed to the spdk_tgt process running within each instance-manager pod. The spdk_tgt process is responsible for handling input/output (IO) operations and requires intensive polling. As a result, it consumes 100% of a dedicated CPU core to efficiently manage and process the IO requests, ensuring optimal performance and responsiveness for storage operations." group: "Longhorn V2 Data Engine (Preview Feature) Settings" type: boolean default: false