script for non-stop looping

[ust3]

I would like to test the CPU loading for a new server , I would like to have a script ( eg. for loop ) that non-stop to run a job eg. copy file , create file etc, this is for testing CPU loading , can advise a script ? thx

[Hasan Atasoy]

hi ;


while true
do
:
done



Hasan

[Torsten.]

You have a lot of different methods to achieve this, but I guess a copy job only will not effect the CPU load that much.

If you run mstm, select the CPU(s) and run the exercise tool, this will put heavy load on the CPU.

[Dennis Handly]

Here is a link for a similar question:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1186172

[Ralph Grothe]

I would think a good way to harness your cpu is to do some number crunching.
Most crypto applications or file packers are good candidates.
You could also try to solve some linear equation systmes as I suppose the notorious lapack is doing.
http://www.netlib.org/lapack/

[Ralph Grothe]

I would think a good way to harness your cpu is to do some number crunching.
Most crypto applications or file packers are good candidates.
You could also try to solve some linear equation systems as I suppose the notorious lapack is doing.
http://www.netlib.org/lapack/

[Ralph Grothe]

I would think a good way to harness your cpu is to do some number crunching.
Most crypto applications or file packers are good candidates.
You could also try to solve some linear equation systems as I suppose the notorious lapack is doing.
http://www.netlib.org/lapack/
Or fluid flow solvers also seem well suited to stress the cpu
http://en.wikipedia.org/wiki/Reynolds-averaged_Navier-Stokes_equations

[Ralph Grothe]

Sorry, for the multi-post.
Webserver didn't respond.

[Geoff Wild]

while true
do
prealloc /someplacewith5gbfree/test.5GB 5368709120
gzip /someplacewith5gbfree/test.5GB
rm /someplacewith5gbfree/test.5GB.gz
done


Something like that...

Rgds...Geoff

[Tim Nelson]

As Hasan stated a loop of null will drive the CPU to the roof. Not the most scientific way but I used it to test CPU allocations for wlm.

The below allows you to start as many as you like to drive all CPUs.


#!/usr/bin/ksh

ii=0
COUNT=${1:-2}
if [[ -z $1 ]]
then
echo "Number not supplied, using default of $COUNT"
else
echo "Using supplied number of $1"
fi

while [[ $ii -lt $COUNT ]]
do
while true
do
:
done &
(( ii = ii + 1 ))
done
jobs -l
echo " to terminate"
read pauz
ii=1
while [[ $ii -le $COUNT ]]
do
echo "Killing % $ii "
kill %$ii
(( ii = ii + 1 ))
done