scx-upstream/meson-scripts/stress_tests.ini

[scx_lavd]
sched: scx_lavd
sched_args:
stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
timeout_sec: 15

[scx_rusty]
sched: scx_rusty
sched_args:
stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
timeout_sec: 15

[scx_rustland]
sched: scx_rustland
sched_args:
stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
timeout_sec: 15

[scx_bpfland]
sched: scx_bpfland
sched_args:
stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
timeout_sec: 15
Add stress-ng to scheduler tests This change adds stress-ng as a load test for schedulers when running in CI. It will run stress-ng while schedulers are being tested with a reasonable amount of work. At the end of the run the stress-ng metrics are collected for later analysis. However, since these results may be running in a VM they may not be super robust. 2024-05-17 15:33:15 +01:00			`[scx_lavd]`
			`sched: scx_lavd`
			`sched_args:`
			stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
			`timeout_sec: 15`

			`[scx_rusty]`
			`sched: scx_rusty`
			`sched_args:`
			stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
			`timeout_sec: 15`

			`[scx_rustland]`
			`sched: scx_rustland`
			`sched_args:`
			stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
			`timeout_sec: 15`
ci: enable stress tests for scx_bpfland Signed-off-by: Andrea Righi <andrea.righi@canonical.com> 2024-06-25 15:17:14 +01:00
			`[scx_bpfland]`
			`sched: scx_bpfland`
			`sched_args:`
			stress_cmd: stress-ng -t 14 --aggressive -M -c `nproc` -f `nproc`
			`timeout_sec: 15`