topic Re: script for non-stop looping in Operating System - HP-UX

script for non-stop looping

ust3 — Fri, 04 Jan 2008 06:04:01 GMT

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

Re: script for non-stop looping

Hasan Atasoy — Fri, 04 Jan 2008 06:32:12 GMT

hi ;

while true
do
:
done

Hasan

Re: script for non-stop looping

Torsten. — Fri, 04 Jan 2008 07:13:50 GMT

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.

Re: script for non-stop looping

Dennis Handly — Fri, 04 Jan 2008 08:06:55 GMT

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

Re: script for non-stop looping

Ralph Grothe — Fri, 04 Jan 2008 13:01:56 GMT

Re: script for non-stop looping

Ralph Grothe — Fri, 04 Jan 2008 13:05:56 GMT

Re: script for non-stop looping

Ralph Grothe — Fri, 04 Jan 2008 13:10:17 GMT

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

Re: script for non-stop looping

Ralph Grothe — Fri, 04 Jan 2008 13:31:49 GMT

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

Re: script for non-stop looping

Geoff Wild — Fri, 04 Jan 2008 19:04:37 GMT

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

Something like that...

Rgds...Geoff

Re: script for non-stop looping

Tim Nelson — Fri, 04 Jan 2008 22:42:29 GMT

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