=== mamarley_ is now known as mamarley === v12aml_ is now known as v12aml [10:09] cking: hiya! How do I prevent stress-ng from running any memory stress tests (since I only have a Gig) but run everything else? [10:09] cking: I tried 'stress-ng -r 4 -x vm --minimize' but I still get several OOMs [10:11] amitk, the only easy way is to exclude all the ones that OOM by the -x option, so that's a a pain [10:13] however, there are quite a few stressors that can trigger OOMs. However, the OOMs won't affect stress-ng, it can respawn the stressors if they get OOM'd [10:13] one can specify per-stressor memory sizes in terms of memory size too (in bytes or % memory available) [10:14] cking: aah, ok. The list of stressors is quite long and there seems to be no easy way to eliminate an entire class of stressors [10:14] amitk, yep, that is a currently a pain point [10:15] cking: doesn't the --minimize flag avoid OOMs be being conservative? [10:15] *by [10:15] amitk, --minimize just selects the lower bounds settings [10:15] that is the opposite of what I thought it does :-) [10:16] I guess I'm looking for max bounds on my memory and IO constrained systems [10:16] but this is a per-test specific setting; some stressors just require a few tens of MB to run effectively [10:16] and that's the lower bounds [10:17] amitk, i suggest running each stressor one by one with a specific memory bound set for the stressors you are interested in [10:17] e.g stress-ng --vm 0 --vm-bytes 80% [10:18] cking: I really want random to catch unexpected errors but was hoping to find a way to say "don't commit beyond 60% of memory" [10:19] amitk, OK, I think one needs to just select the subset of stressors you are interested in and specify the memory size according to your desired constraints on a per-stressor basis [10:19] yep, it's a pain [10:21] cking: ok, thanks. Its been very useful so far to test cpufreq and thermal :-) [10:21] amitk, that's good to know. it can make CPUs run quite hot :-)