# HG changeset patch # User bgruening-util # Date 1614882533 0 # Node ID 254cd55c9900e7d6d074d129066f5e3d630eea16 "planemo upload for repository https://github.com/ColinIanKing/stress-ng commit ffaa4c7cd78355f3c74d1f183729b13a8b6b8bb3" diff -r 000000000000 -r 254cd55c9900 stress_ng.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/stress_ng.xml Thu Mar 04 18:28:53 2021 +0000 @@ -0,0 +1,2896 @@ + + stress test a computer system in various selectable ways + + 0 + 0.12.04 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + stress-ng + + + &1 | tee "$outfile" + + ]]> + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + +
+ + + + +
+
+ +
+ + + + + + + + + + + +
+ + + + +
+
+ +
+ + + + + + + + + + + + +
+ + + + + +
+
+ +
+ + + + + + + + + + + + +
+ + +
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+
+ +
+ + + + + + + + + + + + +
+ + + + +
+
+ +
+ + + + + + + + + + + +
+ + +
+
+ +
+ + + + + + + + + + + + +
+ + + + + + +
+
+ +
+ + + + + + + + + + + +
+ + +
+
+ +
+ + + + + + + + + + + +
+ + + + +
+ + + + + + + + + + +
+ + + +
+
+ + +
+ + + + + + + + + + + +
+ + + +
+
+ +
+ + + + + + + + + + + +
+ + +
+
+ +
+ + + + + + + + + + + + +
+ + +
+ + + + + + + + + + +
+ + +
+ + + + + + + + + + + +
+ + + + +
+ + + + + + + + + + + + + +
+ + + + +
+ + + + + + + + + + + +
+ +
+
+ + +
+ + + + + + + + + + +**Stress-NG** + +``stress-ng`` was originally intended to make a machine work hard and trip hardware +issues such as thermal overruns as well as operating system bugs that only +occur when a system is being thrashed hard. Use stress-ng with caution as some +of the tests can make a system run hot on poorly designed hardware and also can +cause excessive system thrashing which may be difficult to stop. + +stress-ng can also measure test throughput rates; this can be useful to observe +performance changes across different operating system releases or types of +hardware. However, it has never been intended to be used as a precise benchmark +test suite, so do NOT use it in this manner. + +**Examples** + +stress−ng −−vm 8 −−vm−bytes 80% -t 1h + + run 8 virtual memory stressors that combined use 80% of the available memory for 1 hour. Thus each stressor uses 10% of the available memory. + +stress−ng −−cpu 4 −−io 2 −−vm 1 −−vm−bytes 1G −−timeout 60s + + runs for 60 seconds with 4 cpu stressors, 2 io stressors and 1 vm stressor using 1GB of virtual memory. + +stress−ng −−iomix 2 −−iomix−bytes 10% -t 10m + + runs 2 instances of the mixed I/O stressors using a total of 10% of the available file system spacefor 10 minutes. Each stressor will use 5% of the available file system space. + +stress−ng −−cyclic 1 −−cyclic−dist 2500 −−cyclic−method clock_ns −−cyclic−prio 100 −−cyclic−sleep 10000 −−hdd 0 -t 1m + + measures real time scheduling latencies created by the hdd stressor.This uses the high resolution nanosecond clock to measure latencies during sleeps of 10,000 nanoseconds. + At the end of 1minute of stressing, the latency distribution with 2500 ns intervals will be displayed. + + NOTE: this must be run with the ``CAP_SYS_NICE`` capability to enable the real time scheduling to get accurate measurements. + +stress−ng −−cpu 8 −−cpu−ops 800000 + + runs 8 cpu stressors and stops after 800000 bogo operations. + +stress−ng −−sequential 2 −−timeout 2m −−metrics + + run 2 simultaneous instances of all the stressors sequentially one by one, each for 2 minutes andsummarise with performance metrics at the end. + +stress−ng −−cpu 4 −−cpu-method fft −−cpu-ops 10000 −−metrics−brief + + run 4 FFT cpu stressors, stop after 10000 bogo operations and produce a summary just for the FFTresults. + +stress−ng −−cpu -1 −−cpu-method all −t 1h −−cpu−load 90 + + run cpu stressors on all online CPUs working through all the available CPU stressors for 1 hour, loading the CPUs at 90% load capacity. + +stress−ng −−cpu 0 −−cpu-method all −t 20m + + run cpu stressors on all configured CPUs working through all the available CPU stressors for 20minutes + +stress−ng −−all 4 −−timeout 5m + + run 4 instances of all the stressors for 5 minutes. + +stress−ng −−random 64 + + run 64 stressors that are randomly chosen from all the available stressors. + +stress−ng −−cpu 64 −−cpu−method all −−verify −t 10m −−metrics−brief + + run 64 instances of all the different cpu stressors and verify that the computations are correct for 10 minutes with a bogo operations summary at the end. + +stress−ng −−sequential -1 −t 10m + + run all the stressors one by one for 10 minutes, with the number of instances of each stressor matching the number of online CPUs. + +stress−ng −−sequential 8 −−class io −t 5m −−times + + run all the stressors in the io class one by one for 5 minutes each, with 8 instances of each stressor running concurrently and show overall time utilisation statistics at the end of the run. + +stress−ng −−all -1 −−maximize −−aggressive + + run all the stressors (1 instance of each per online CPU) simultaneously,maximize the settings(memory sizes, file allocations, etc.) and select the most demanding/aggressive options. + +stress−ng −−random 32 −x numa,hdd,key + + run 32 randomly selected stressors and exclude the numa, hdd and key stressors + +stress−ng −−sequential 4 −−class vm −−exclude bigheap,brk,stack + + run 4 instances of the VM stressors one after each other, excluding the bigheap, brk and stack stressors + +stress−ng −−taskset 0,2-3 −−cpu 3 + + run 3 instances of the CPU stressor and pin them to CPUs 0, 2 and 3. + + +