Stressing libreelec via tools in ssh (or somewhere in Kodi)

Apologies if this is posted in the wrong location, this is my first post here. Please feel free to move it to wherever it should go.

I have Libreelec 12.0.1 running on a Raspberry Pi 4. I want to run a stress test, to test out the fan curves of a new case I've just acquired and the overclocking settings I've tried to enable.

Try as I might, I cannot find any information anywhere about what tool I could run to stress my device, and maybe this comes down to Libreelec's stripped-down OS?

I think I want to run stress-ng, but my terminal tells me it isn't installed and I do not know how to add it via terminal (e.g. no apt or apt-get available). I do have the system-tools Addon installed in Kodi, but I don't know how to access the version of stress-ng that is apparently installed with it, either inside of Kodi or via an ssh terminal.

The reason I'm attempting all this via terminal is because I'm already using watch -n 1 vcgencmd measure_temp to monitor its temp.

My goal is to stress my CPU cores so I can confirm the overclock setting and fan curves, so if someone thinks there's a better way to go about this in my case, I'd very much appreciate the advice.

Thank you! openssl speed -multi 4 worked for me!

But for information (in case this is an actual issue I've found), no combination of ssh disconnecting/reconnecting, Addon uninstalling/installing, and rebooting/powering completely off and then back on, has gotten stress-ng to be accessible from the default $PATH.

I did go looking through the file structure and found a file named "stress-ng" in /storage/.kodi/addons/virtual.system-tools/bin/, but relocating to this directory and then running it turned up the error: line 0: syntax error: unexpected word (expecting ")"). I have no idea if this means anything though, because obviously this isn't the correct way to run stress-ng, but just in case it means something, I thought I'd report it here.

Anyway, thank you for your help!

To update after my last response: there was definitely something wrong with my installation. An update of PINN Lite failed, which led me to a required full reformatting and reinstall, and after the reinstall, I have no trouble using stress-ng in my terminal. There are no remaining mysteries with my circumstances.