Is stress-ng likely to cover stress scenarios of prime95, FIRESTARTER, etc? #246
-
|
Hi and thanks @ColinIanKing for the great project! I want to create a process for verifying the stability, correctness, and performance of hardware. This is mainly useful for me to verify new hardware I buy (laptop, RAM, etc.). My current plan is roughly:
I have two questions:
Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Hi there, The plan sounds very rational to me. It does make sense to add other tools as they do cover areas that stress-ng does not cover. For example, MemTest86 will have far better physical memory testing since stress-ng can only access memory via linear virtual addressing. Also, test like prim95 can't be added to stress-ng as this is copyrighted code and stress-ng is written from scratch and does not import other licenced/copyrighted code into the source tree. Colin |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot @ColinIanKing ! |
Beta Was this translation helpful? Give feedback.
-
|
Hello @ColinIanKing, Recently when I run the stress test in checkbox, it seems that the oom-killer will be triggered when run the mlock test in Checkbox. The kernel log looks like this: Apr 11 01:45:01 Jaguar3-2 CRON[7390]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Do you have any idea about this?Any hints will be appreciated. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
|
The mlock stressor tries to lock pages into memory so that they cannot be swapped out. The error you are seeing is because the kernel has run out of physical pages to provide the virtual memory pages as requested by stress-ng. When memory is low the kernel out of memory (OOM) killer tries to kill the memory hogging process. You could try --oom-avoid or --oomable options to try and reduce the OOMing |
Beta Was this translation helpful? Give feedback.
Hi there,
The plan sounds very rational to me. It does make sense to add other tools as they do cover areas that stress-ng does not cover. For example, MemTest86 will have far better physical memory testing since stress-ng can only access memory via linear virtual addressing. Also, test like prim95 can't be added to stress-ng as this is copyrighted code and stress-ng is written from scratch and does not import other licenced/copyrighted code into the source tree.
Colin