Linux JVM CPU stress
Linux JVM CPU stress consumes excessive CPU threads of the JVM.
JVM chaos faults use the Byteman utility to inject chaos faults into the JVM.
Use cases
Linux JVM CPU stress:
- Tests the system's ability to handle high payloads.
- Evaluates the application's behavior in high-stress cases.
- Induces CPU consumption and exhaustion on the target Java process JVM.
- Simulates a lack of CPU threads for processes running on the application, which degrades their performance.
- Simulates application slowness due to CPU starvation.
- This fault can be executed on Ubuntu 16 or higher, Debian 10 or higher, CentOS 7 or higher, RHEL 7 or higher, Fedora 30 or higher, and openSUSE LEAP 15.4 or higher.
- The
linux-chaos-infrastructure
systemd service should be in an active state, and the infrastructure should be inCONNECTED
state.
Fault permissions
The fault uses the root
Linux user and root
user group.
Mandatory tunables
Tunable | Description | Notes |
---|---|---|
cpu | The number of CPU threads that the application should consume. | For example, 4. For more information, go to CPU threads. |
pid | The process ID that Byteman uses to target the service. This is mutually exclusive with startupCommand. If pid is specified (other than 0), startupCommand is not required. | For example, 6429 . For more information, go to process Ids. |
startupCommand | The command used to start the Java process. A substring match is used with the given command for all processes. This is mutually exclusive with pid. | If startupCommand is specified, you need to set pid to 0. For example, /usr/local/bin/pet-clinic.jar . For more information, go to startup command. |
Optional tunables
Tunable | Description | Notes |
---|---|---|
duration | Duration through which chaos is injected into the target resource. Should be provided in [numeric-hours]h[numeric-minutes]m[numeric-seconds]s format. | Default: 30s . Examples: 1m25s , 1h3m2s , 1h3s . For more information, go to duration of the chaos. |
port | Port used by the Byteman agent. | Default: 9091 . |
rampTime | Period to wait before and after injecting chaos. Should be provided in [numeric-hours]h[numeric-minutes]m[numeric-seconds]s format. | Default: 0s . Examples: 1m25s , 1h3m2s , 1h3s . For more information, go to ramp time. |
Pid
The process ID used by Byteman to target the services of the JVM. This is mutually exclusive with the startupCommand
input variable.
The following YAML snippet illustrates the use of this input variable:
apiVersion: litmuchaos.io/v1alpha1
kind: LinuxFault
metadata:
name: linux-jvm-cpu-stress
labels:
name: jvm-cpu-stress
spec:
jvmChaos/inputs:
duration: 30s
port: 9091
pid: 1
cpu: 2
rampTime: ""
Startup command
The command used to start the Java process. A substring match is used with the given command for all processes. This is mutually exclusive with the pid
input variable.
The following YAML snippet illustrates the use of this input variable:
apiVersion: litmuchaos.io/v1alpha1
kind: LinuxFault
metadata:
name: linux-jvm-cpu-stress
labels:
name: jvm-cpu-stress
spec:
jvmChaos/inputs:
duration: 30s
port: 9091
pid: 0
cpu: 2
startupCommand: "/usr/bin/pet-clinic.jar"
rampTime: ""
CPU threads
The number of CPU threads used to simulate excessive CPU usage.
The following YAML snippet illustrates the use of this input variable:
apiVersion: litmuchaos.io/v1alpha1
kind: LinuxFault
metadata:
name: linux-jvm-cpu-stress
labels:
name: jvm-cpu-stress
spec:
jvmChaos/inputs:
duration: 30s
port: 9091
pid: 0
cpu: 2
startupCommand: "/usr/bin/pet-clinic.jar"
rampTime: ""