From 57ec0b76f8c48f0ea02735b40a312f62cae6c2e3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E9=9C=84=E7=A3=8A?= <xiaolei.zl@alibaba-inc.com>
Date: Tue, 11 Jun 2024 10:44:19 +0800
Subject: [PATCH] increase memroy request

---
 charts/graphscope-interactive/values.yaml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/charts/graphscope-interactive/values.yaml b/charts/graphscope-interactive/values.yaml
index 7239bc977527..f38a5a69715c 100644
--- a/charts/graphscope-interactive/values.yaml
+++ b/charts/graphscope-interactive/values.yaml
@@ -197,11 +197,11 @@ primary:
   ##
   resources: 
     limits:
-      cpu: 1000m
-      memory: 8Gi
+      cpu: 16000m
+      memory: 32Gi
     requests:
-      cpu: 1000m
-      memory: 8Gi
+      cpu: 8000m
+      memory: 16Gi
     # We usually recommend not to specify default resources and to leave this as a conscious
     # choice for the user. This also increases chances charts run on environments with little
     # resources, such as Minikube. If you do want to specify resources, uncomment the following
@@ -434,11 +434,11 @@ secondary:
   ##
   resources: 
     limits:
-      cpu: 8000m
-      memory: 10Gi
+      cpu: 320000m
+      memory: 200Gi
     requests:
-      cpu: 8000m
-      memory: 10Gi
+      cpu: 32000m
+      memory: 200Gi
     # We usually recommend not to specify default resources and to leave this as a conscious
     # choice for the user. This also increases chances charts run on environments with little
     # resources, such as Minikube. If you do want to specify resources, uncomment the following