Skip to content

armgit / core

Public Imported from GitHub
0

100% open-source IoT Platform - Integrate your devices, add intelligence, build custom apps

Add several profiles with bigger setups used in load testing and pushing system to the limits (#2500)

Eric Bariaux8b89e67b1d3e
diff --git a/test/load2-eks/README.md b/test/load2-eks/README.md
index dfa56cd6e..6d6454841 100644
--- a/test/load2-eks/README.md
+++ b/test/load2-eks/README.md
@@ -6,8 +6,11 @@ and adapting the values files to configure the memory usage on the different pod
For the manager, JVM parameters are used to make use of the extra memory available to the container.
There are different "profiles" available depending on the power required and the tests to be run:
- large: minimal set-up useful to test memory leaks and pressure condition
-- xlarge: doubles memory allocation for manager compared to large profile (4Gi vs 2Gi), with room for further increases
-- 2xlarge: much bigger setup to test system limits and get a feel for performance level we can reach
+- xlarge-minimal: doubles memory allocation for manager compared to large profile (4Gi vs 2Gi), with room for further increases
+- xlarge: bigger setup using all capacity on 4 CPU/16 GB cluster
+- 2xlarge: bigger setup using all capacity on 8 CPU/32 GB cluster
+- 4xlarge: bigger setup using all capacity on 16 CPU/64 GB cluster
+- 8xlarge: bigger setup using all capacity on 32 CPU/128 GB cluster
The profile is selected by setting the OR_PROFILE environment variable in the `eks-common.sh` script.
diff --git a/test/load2-eks/profiles/4xlarge/README.md b/test/load2-eks/profiles/4xlarge/README.md
new file mode 100644
index 000000000..ec71cc3f4
--- /dev/null
+++ b/test/load2-eks/profiles/4xlarge/README.md
@@ -0,0 +1 @@
+Cluster using 1 m8g.4xlarge VM
diff --git a/test/load2-eks/profiles/4xlarge/cluster.yaml b/test/load2-eks/profiles/4xlarge/cluster.yaml
new file mode 100644
index 000000000..533b77b28
--- /dev/null
+++ b/test/load2-eks/profiles/4xlarge/cluster.yaml
@@ -0,0 +1,35 @@
+apiVersion: eksctl.io/v1alpha5
+kind: ClusterConfig
+
+metadata:
+ name: ${CLUSTER_NAME}
+ region: ${AWS_REGION}
+ # Kubernetes version to use for cluster, good idea to keep up to date
+ version: "1.34"
+
+availabilityZones:
+ - ${AWS_REGION}a
+ - ${AWS_REGION}b
+
+iam:
+ withOIDC: true
+ serviceAccounts:
+ - metadata:
+ name: aws-load-balancer-controller
+ namespace: kube-system
+ wellKnownPolicies:
+ awsLoadBalancerController: true
+
+nodeGroups:
+ - name: ng-1
+ instanceType: m8g.4xlarge
+ volumeSize: 32
+ desiredCapacity: 1
+ availabilityZones:
+ - ${AWS_REGION}a
+
+addons:
+ - name: aws-ebs-csi-driver
+ version: latest
+ wellKnownPolicies:
+ ebsCSIController: true
diff --git a/test/load2-eks/profiles/4xlarge/values-keycloak-eks-load.yaml b/test/load2-eks/profiles/4xlarge/values-keycloak-eks-load.yaml
new file mode 100644
index 000000000..3ddd56060
--- /dev/null
+++ b/test/load2-eks/profiles/4xlarge/values-keycloak-eks-load.yaml
@@ -0,0 +1,7 @@
+resources:
+ limits:
+ cpu: 2000m
+ memory: 5Gi
+ requests:
+ cpu: 2000m
+ memory: 5Gi
diff --git a/test/load2-eks/profiles/4xlarge/values-manager-eks-load.yaml b/test/load2-eks/profiles/4xlarge/values-manager-eks-load.yaml
new file mode 100644
index 000000000..0066b3ed1
--- /dev/null
+++ b/test/load2-eks/profiles/4xlarge/values-manager-eks-load.yaml
@@ -0,0 +1,57 @@
+image:
+ pullPolicy: Always
+ tag: "load2"
+
+livenessProbe:
+ httpGet:
+ path: /
+ port: 8080
+ periodSeconds: 5
+readinessProbe:
+ httpGet:
+ path: /
+ port: 8080
+ periodSeconds: 5
+startupProbe:
+ httpGet:
+ path: /
+ port: 8080
+ failureThreshold: 1000
+ periodSeconds: 10
+
+service:
+ jmx:
+ enabled: true
+
+resources:
+ limits:
+ cpu: 8000m
+ memory: 38Gi
+ requests:
+ cpu: 8000m
+ memory: 38Gi
+
+volumeSize: "16Gi"
+
+or:
+ env:
+ - name: OR_SETUP_USERS
+ value: "1000"
+ - name: OR_SETUP_ASSETS
+ value: "5"
+ - name: OR_SETUP_ASSETS_WITH_LOCATIONS
+ value: "4"
+ - name: OR_SETUP_LOCATION_CLUSTERS
+ value: "5"
+ - name: OR_SETUP_LOCATION_MAIN_CENTER
+ value: "4.469444,51.925"
+ - name: OR_SETUP_LOCATION_CENTER_DISTANCE
+ value: "3000"
+ - name: OR_SETUP_LOCATION_ASSET_RADIUS
+ value: "500"
+ - name: OR_SETUP_STORE_DATA_POINTS
+ value: "false"
+ - name: OR_JAVA_OPTS
+ value: "-Dhibernate.generate_statistics=true -XX:InitialRAMPercentage=75 -XX:MaxRAMPercentage=75 -XX:NativeMemoryTracking=summary -Xlog:all=warning:stdout:uptime,level,tags -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/dump.hprof -Xlog:gc*,gc+ref=debug,gc+phases=debug,gc+age=debug,safepoint:file=gc.log"
+ - name: JAVA_TOOL_OPTIONS
+ value: "-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=8085 -Dcom.sun.management.jmxremote.rmi.port=8085 -Djava.rmi.server.hostname=localhost"
diff --git a/test/load2-eks/profiles/4xlarge/values-postgresql-eks-load.yaml b/test/load2-eks/profiles/4xlarge/values-postgresql-eks-load.yaml
new file mode 100644
index 000000000..a96b0791a
--- /dev/null
+++ b/test/load2-eks/profiles/4xlarge/values-postgresql-eks-load.yaml
@@ -0,0 +1,9 @@
+volumeSize: "16Gi"
+
+resources:
+ limits:
+ cpu: 2500m
+ memory: 6Gi
+ requests:
+ cpu: 2500m
+ memory: 6Gi
diff --git a/test/load2-eks/profiles/4xlarge/values-proxy-eks-load.yaml b/test/load2-eks/profiles/4xlarge/values-proxy-eks-load.yaml
new file mode 100644
index 000000000..41fb409d2
--- /dev/null
+++ b/test/load2-eks/profiles/4xlarge/values-proxy-eks-load.yaml
@@ -0,0 +1,7 @@
+resources:
+ limits:
+ cpu: 2000m
+ memory: 6Gi
+ requests:
+ cpu: 2000m
+ memory: 6Gi
diff --git a/test/load2-eks/profiles/8xlarge/README.md b/test/load2-eks/profiles/8xlarge/README.md
new file mode 100644
index 000000000..f3b7edc40
--- /dev/null
+++ b/test/load2-eks/profiles/8xlarge/README.md
@@ -0,0 +1 @@
+Cluster using 1 m8g.8xlarge VM
diff --git a/test/load2-eks/profiles/8xlarge/cluster.yaml b/test/load2-eks/profiles/8xlarge/cluster.yaml
new file mode 100644
index 000000000..4aa30b453
--- /dev/null
+++ b/test/load2-eks/profiles/8xlarge/cluster.yaml
@@ -0,0 +1,35 @@
+apiVersion: eksctl.io/v1alpha5
+kind: ClusterConfig
+
+metadata:
+ name: ${CLUSTER_NAME}
+ region: ${AWS_REGION}
+ # Kubernetes version to use for cluster, good idea to keep up to date
+ version: "1.34"
+
+availabilityZones:
+ - ${AWS_REGION}a
+ - ${AWS_REGION}b
+
+iam:
+ withOIDC: true
+ serviceAccounts:
+ - metadata:
+ name: aws-load-balancer-controller
+ namespace: kube-system
+ wellKnownPolicies:
+ awsLoadBalancerController: true
+
+nodeGroups:
+ - name: ng-1
+ instanceType: m8g.8xlarge
+ volumeSize: 32
+ desiredCapacity: 1
+ availabilityZones:
+ - ${AWS_REGION}a
+
+addons:
+ - name: aws-ebs-csi-driver
+ version: latest
+ wellKnownPolicies:
+ ebsCSIController: true
diff --git a/test/load2-eks/profiles/8xlarge/values-keycloak-eks-load.yaml b/test/load2-eks/profiles/8xlarge/values-keycloak-eks-load.yaml
new file mode 100644
index 000000000..22ca73363
--- /dev/null
+++ b/test/load2-eks/profiles/8xlarge/values-keycloak-eks-load.yaml
@@ -0,0 +1,7 @@
+resources:
+ limits:
+ cpu: 3000m
+ memory: 6Gi
+ requests:
+ cpu: 3000m
+ memory: 6Gi
diff --git a/test/load2-eks/profiles/8xlarge/values-manager-eks-load.yaml b/test/load2-eks/profiles/8xlarge/values-manager-eks-load.yaml
new file mode 100644
index 000000000..402b2d6ba
--- /dev/null
+++ b/test/load2-eks/profiles/8xlarge/values-manager-eks-load.yaml
@@ -0,0 +1,57 @@
+image:
+ pullPolicy: Always
+ tag: "load2"
+
+livenessProbe:
+ httpGet:
+ path: /
+ port: 8080
+ periodSeconds: 5
+readinessProbe:
+ httpGet:
+ path: /
+ port: 8080
+ periodSeconds: 5
+startupProbe:
+ httpGet:
+ path: /
+ port: 8080
+ failureThreshold: 1000
+ periodSeconds: 10
+
+service:
+ jmx:
+ enabled: true
+
+resources:
+ limits:
+ cpu: 18000m
+ memory: 68Gi
+ requests:
+ cpu: 18000m
+ memory: 68Gi
+
+volumeSize: "16Gi"
+
+or:
+ env:
+ - name: OR_SETUP_USERS
+ value: "50000"
+ - name: OR_SETUP_ASSETS
+ value: "5"
+ - name: OR_SETUP_ASSETS_WITH_LOCATIONS
+ value: "0"
+ - name: OR_SETUP_LOCATION_CLUSTERS
+ value: "0"
+ - name: OR_SETUP_LOCATION_MAIN_CENTER
+ value: "0,0"
+ - name: OR_SETUP_LOCATION_CENTER_DISTANCE
+ value: "0"
+ - name: OR_SETUP_LOCATION_ASSET_RADIUS
+ value: "0"
+ - name: OR_SETUP_STORE_DATA_POINTS
+ value: "false"
+ - name: OR_JAVA_OPTS
+ value: "-Dhibernate.generate_statistics=true -XX:InitialRAMPercentage=75 -XX:MaxRAMPercentage=75 -XX:NativeMemoryTracking=summary -Xlog:all=warning:stdout:uptime,level,tags -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/dump.hprof -Xlog:gc*,gc+ref=debug,gc+phases=debug,gc+age=debug,safepoint:file=gc.log"
+ - name: JAVA_TOOL_OPTIONS
+ value: "-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=8085 -Dcom.sun.management.jmxremote.rmi.port=8085 -Djava.rmi.server.hostname=localhost"
diff --git a/test/load2-eks/profiles/8xlarge/values-postgresql-eks-load.yaml b/test/load2-eks/profiles/8xlarge/values-postgresql-eks-load.yaml
new file mode 100644
index 000000000..57dce1e33
--- /dev/null
+++ b/test/load2-eks/profiles/8xlarge/values-postgresql-eks-load.yaml
@@ -0,0 +1,9 @@
+volumeSize: "16Gi"
+
+resources:
+ limits:
+ cpu: 4000m
+ memory: 10Gi
+ requests:
+ cpu: 4000m
+ memory: 10Gi
diff --git a/test/load2-eks/profiles/8xlarge/values-proxy-eks-load.yaml b/test/load2-eks/profiles/8xlarge/values-proxy-eks-load.yaml
new file mode 100644
index 000000000..0db708a35
--- /dev/null
+++ b/test/load2-eks/profiles/8xlarge/values-proxy-eks-load.yaml
@@ -0,0 +1,7 @@
+resources:
+ limits:
+ cpu: 4000m
+ memory: 10Gi
+ requests:
+ cpu: 4000m
+ memory: 10Gi
diff --git a/test/load2-eks/profiles/xlarge-minimal/README.md b/test/load2-eks/profiles/xlarge-minimal/README.md
new file mode 100644
index 000000000..c7f052274
--- /dev/null
+++ b/test/load2-eks/profiles/xlarge-minimal/README.md
@@ -0,0 +1,3 @@
+Cluster using 1 m8g.xlarge VM
+Still running the stack with limited CPU and memory.
+Mostly slightly increasing memory over large version to check what the impact is on MQTT queue backlog.
diff --git a/test/load2-eks/profiles/xlarge-minimal/cluster.yaml b/test/load2-eks/profiles/xlarge-minimal/cluster.yaml
new file mode 100644
index 000000000..f5d60c9f4
--- /dev/null
+++ b/test/load2-eks/profiles/xlarge-minimal/cluster.yaml
@@ -0,0 +1,35 @@
+apiVersion: eksctl.io/v1alpha5
+kind: ClusterConfig
+
+metadata:
+ name: ${CLUSTER_NAME}
+ region: ${AWS_REGION}
+ # Kubernetes version to use for cluster, good idea to keep up to date
+ version: "1.34"
+
+availabilityZones:
+ - ${AWS_REGION}a
+ - ${AWS_REGION}b
+
+iam:
+ withOIDC: true
+ serviceAccounts:
+ - metadata:
+ name: aws-load-balancer-controller
+ namespace: kube-system
+ wellKnownPolicies:
+ awsLoadBalancerController: true
+
+nodeGroups:
+ - name: ng-1
+ instanceType: m8g.xlarge
+ volumeSize: 32
+ desiredCapacity: 1
+ availabilityZones:
+ - ${AWS_REGION}a
+
+addons:
+ - name: aws-ebs-csi-driver
+ version: latest
+ wellKnownPolicies:
+ ebsCSIController: true
diff --git a/test/load2-eks/profiles/xlarge-minimal/values-keycloak-eks-load.yaml b/test/load2-eks/profiles/xlarge-minimal/values-keycloak-eks-load.yaml
new file mode 100644
index 000000000..41bfda1b4
--- /dev/null
+++ b/test/load2-eks/profiles/xlarge-minimal/values-keycloak-eks-load.yaml
@@ -0,0 +1,7 @@
+resources:
+ limits:
+ cpu: 280m
+ memory: 512Mi
+ requests:
+ cpu: 280m
+ memory: 512Mi
diff --git a/test/load2-eks/profiles/xlarge-minimal/values-manager-eks-load.yaml b/test/load2-eks/profiles/xlarge-minimal/values-manager-eks-load.yaml
new file mode 100644
index 000000000..c53a17de3
--- /dev/null
+++ b/test/load2-eks/profiles/xlarge-minimal/values-manager-eks-load.yaml
@@ -0,0 +1,57 @@
+image:
+ pullPolicy: Always
+ tag: "load2"
+
+livenessProbe:
+ httpGet:
+ path: /
+ port: 8080
+ periodSeconds: 5
+readinessProbe:
+ httpGet:
+ path: /
+ port: 8080
+ periodSeconds: 5
+startupProbe:
+ httpGet:
+ path: /
+ port: 8080
+ failureThreshold: 500
+ periodSeconds: 10
+
+service:
+ jmx:
+ enabled: true
+
+resources:
+ limits:
+ cpu: 400m
+ memory: 4Gi
+ requests:
+ cpu: 400m
+ memory: 4Gi
+
+volumeSize: "16Gi"
+
+or:
+ env:
+ - name: OR_SETUP_USERS
+ value: "1000"
+ - name: OR_SETUP_ASSETS
+ value: "5"
+ - name: OR_SETUP_ASSETS_WITH_LOCATIONS
+ value: "0"
+ - name: OR_SETUP_LOCATION_CLUSTERS
+ value: "0"
+ - name: OR_SETUP_LOCATION_MAIN_CENTER
+ value: "0,0"
+ - name: OR_SETUP_LOCATION_CENTER_DISTANCE
+ value: "0"
+ - name: OR_SETUP_LOCATION_ASSET_RADIUS
+ value: "0"
+ - name: OR_SETUP_STORE_DATA_POINTS
+ value: "false"
+ - name: OR_JAVA_OPTS
+ value: "-Dhibernate.generate_statistics=true -XX:InitialRAMPercentage=75 -XX:MaxRAMPercentage=75 -XX:NativeMemoryTracking=summary -Xlog:all=warning:stdout:uptime,level,tags -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/dump.hprof -Xlog:gc*,gc+ref=debug,gc+phases=debug,gc+age=debug,safepoint:file=gc.log"
+ - name: JAVA_TOOL_OPTIONS
+ value: "-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=8085 -Dcom.sun.management.jmxremote.rmi.port=8085 -Djava.rmi.server.hostname=localhost"
diff --git a/test/load2-eks/profiles/xlarge-minimal/values-postgresql-eks-load.yaml b/test/load2-eks/profiles/xlarge-minimal/values-postgresql-eks-load.yaml
new file mode 100644
index 000000000..ce6c97c90
--- /dev/null
+++ b/test/load2-eks/profiles/xlarge-minimal/values-postgresql-eks-load.yaml
@@ -0,0 +1,9 @@
+volumeSize: "16Gi"
+
+resources:
+ limits:
+ cpu: 350m
+ memory: 1Gi
+ requests:
+ cpu: 350m
+ memory: 1Gi
diff --git a/test/load2-eks/profiles/xlarge-minimal/values-proxy-eks-load.yaml b/test/load2-eks/profiles/xlarge-minimal/values-proxy-eks-load.yaml
new file mode 100644
index 000000000..83704321d
--- /dev/null
+++ b/test/load2-eks/profiles/xlarge-minimal/values-proxy-eks-load.yaml
@@ -0,0 +1,7 @@
+resources:
+ limits:
+ cpu: 200m
+ memory: 512Mi
+ requests:
+ cpu: 200m
+ memory: 512Mi
diff --git a/test/load2-eks/profiles/xlarge/README.md b/test/load2-eks/profiles/xlarge/README.md
index c7f052274..3a65eb5dd 100644
--- a/test/load2-eks/profiles/xlarge/README.md
+++ b/test/load2-eks/profiles/xlarge/README.md
@@ -1,3 +1 @@
-Cluster using 1 m8g.xlarge VM
-Still running the stack with limited CPU and memory.
-Mostly slightly increasing memory over large version to check what the impact is on MQTT queue backlog.
+Cluster using 1 m8g.xlarge VM
diff --git a/test/load2-eks/profiles/xlarge/values-keycloak-eks-load.yaml b/test/load2-eks/profiles/xlarge/values-keycloak-eks-load.yaml
index 41bfda1b4..c9c050969 100644
--- a/test/load2-eks/profiles/xlarge/values-keycloak-eks-load.yaml
+++ b/test/load2-eks/profiles/xlarge/values-keycloak-eks-load.yaml
@@ -1,7 +1,7 @@
resources:
limits:
- cpu: 280m
- memory: 512Mi
+ cpu: 500m
+ memory: 1Gi
requests:
- cpu: 280m
- memory: 512Mi
+ cpu: 500m
+ memory: 1Gi
diff --git a/test/load2-eks/profiles/xlarge/values-manager-eks-load.yaml b/test/load2-eks/profiles/xlarge/values-manager-eks-load.yaml
index 28e309370..eed3b9868 100644
--- a/test/load2-eks/profiles/xlarge/values-manager-eks-load.yaml
+++ b/test/load2-eks/profiles/xlarge/values-manager-eks-load.yaml
@@ -25,11 +25,11 @@ service:
resources:
limits:
- cpu: 400m
- memory: 4Gi
+ cpu: 1500m
+ memory: 8Gi
requests:
- cpu: 400m
- memory: 4Gi
+ cpu: 1500m
+ memory: 8Gi
volumeSize: "16Gi"
diff --git a/test/load2-eks/profiles/xlarge/values-postgresql-eks-load.yaml b/test/load2-eks/profiles/xlarge/values-postgresql-eks-load.yaml
index ce6c97c90..b46ba7c2a 100644
--- a/test/load2-eks/profiles/xlarge/values-postgresql-eks-load.yaml
+++ b/test/load2-eks/profiles/xlarge/values-postgresql-eks-load.yaml
@@ -2,8 +2,8 @@ volumeSize: "16Gi"
resources:
limits:
- cpu: 350m
- memory: 1Gi
+ cpu: 800m
+ memory: 2Gi
requests:
- cpu: 350m
- memory: 1Gi
+ cpu: 800m
+ memory: 2Gi
diff --git a/test/load2-eks/profiles/xlarge/values-proxy-eks-load.yaml b/test/load2-eks/profiles/xlarge/values-proxy-eks-load.yaml
index 83704321d..474c6c0f9 100644
--- a/test/load2-eks/profiles/xlarge/values-proxy-eks-load.yaml
+++ b/test/load2-eks/profiles/xlarge/values-proxy-eks-load.yaml
@@ -1,7 +1,7 @@
resources:
limits:
- cpu: 200m
+ cpu: 400m
memory: 512Mi
requests:
- cpu: 200m
+ cpu: 400m
memory: 512Mi