Is there a way within audacity to control its processing to a fraction of its accessing system's resources, like CPU usage, RAM, HDD, etc.?

Is there a way to throttle audacity internally?
RAM has become very expensive of late. My technician tells me that the price may come down after a few months. Until that time, I am a bit limited with a HP OMEN Gaming Laptop with 8GB memory. The system comes to almost a standstill when audacity uses batch process to process long audios, of about 40-60 MB m4a audio files.
Until that time, I am compelled to throttle audacity externally through the following script file:
######################
#!/bin/bash
###########
Note: Use code below:
'# su
'#### ./audacity_throttle.sh 200 800
'# Usage: ./audacity_throttle.sh [run_ms] [pause_ms]
'# Default: run 200ms, pause 800ms
'###########
'# Then if not required, kill the script with:
'#### kill -CONT $(pidof audacity)
'###########
RUN_MS=${1:-200}
PAUSE_MS=${2:-800}

PID=$(pidof audacity)

if [ -z “$PID” ]; then
echo “Audacity not running”
exit 1
fi

echo “Controlling PID: $PID (run=${RUN_MS}ms pause=${PAUSE_MS}ms)”

while kill -0 $PID 2>/dev/null; do
kill -STOP $PID
sleep $(awk “BEGIN {print $PAUSE_MS/1000}”)
kill -CONT $PID
sleep $(awk “BEGIN {print $RUN_MS/1000}”)
done

echo “Audacity exited”
######################
But is there a way within audacity to control its processing to a fraction of its accessing system’s resources, like CPU usage, RAM, HDD, etc.?

On a Windows system, messing with priority will make a difference to the Audacity program, but affinity makes no difference because Audacity only accesses one CPU. I am not sure if that is still true on version 4 of Audacity.

ChatGPT tells me Audacity4 still only uses one CPU, (even if you have 8).