Ok. This script isn't near as cool as the last one. But it still should be very effective. I just don't want to reinvent the wheel and redo the one I accidentally deleted.. Anyways here is the script:
Code:
##################################################################################
##################Pilots of America Server Test Script############################
############################Jesse Angell##########################################
##################################################################################
##################################################################################
###This function first removes leftovers from failed previous run attempts########
###it will then make a copy of the testfile to use for this benchmark run#########
###after that it will time how long it takes to compress with gzip################
###it'll now remove that gzip file as we no longer need it########################
##################################################################################
function cputest() {
rm /home/test/testfile_go.gz >/dev/null 2>&1
cp /home/test/testfile /home/test/testfile_go >/dev/null 2>&1
/usr/bin/time -f '%e' -o /home/test/time gzip /home/test/testfile_go
rm /home/test/testfile_go.gz >/dev/null 2>&1
}
##################################################################################
###This function pings google and strips the results for the time it took and#####
###puts that number into a variable for later use in this script##################
##################################################################################
function pingtest() {
pingtest=`ping google.com -c 1 |grep time= |awk '{print $7}' |awk -F = '{print $2}'`
}
##################################################################################
###this function is used to log the actual results of the test into a text file###
###we call the above two functions and use echo to place them in a human readable#
###format into /home/test/testresults.log after which it will remove the file#####
###with the saved cpu benchmark time as it's no longer needed#####################
##################################################################################
function logresult() {
pingtest
cputest
echo "`date` Ping Time: `echo "$pingtest"` CPU Time: `cat /home/test/time`" >> /home/test/testresults.log
rm /home/test/time >/dev/null 2>&1
}
###################################################################################
###This if statement is pretty simple and launches everything above. first it#####
###checks to see if we have a 50MB test file to compress for benchmarks. if#######
###we do not it will generate one randomily using dd and /dev/unrandom.############
###it's important to never delete the testfile as our results could be ############
###changed if this is forced to generate a new test file###########################
###################################################################################
if [ -f /home/test/testfile ]
then
logresult
else
dd if=/dev/urandom of=./testfile bs=1024 count=51200 >/dev/null 2>&1
logresult
fi
It is a very safe script. I tested/develoepd it on Redhat ES 4. It took my system about 6 seconds to run the cpu test. You can make hte test more stressfull by increasing the number in dd. from 51,000 to 100,000 or so would about double the time...
Here are some basic instructions for you to deploy this:
/usr/sbin/adduser test
su test
cd /home/test
wget
http://www.jesseangell.com/test
chmod 755 -Rf /home/test/test
That will pretty much get the script rolling. You can test it by typing:
/home/test/test .. That will generate a log file at /home/test/testresults.log.
In order for this to be effective you need to add it to cron so that it will run itself every few minutes. As the user: test type the following:
crontab -e
That will bring up the crontab in vi. Press
i on your keyboard and type in:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /home/test/test
Now press:
SHIFT :
Type in:
wq! and press enter. This will now run every five minutes.
The basic theory behind this script is pretty simple. This will allow you to watch the actual performance of the server. It's impossible for you to really know what's going on unless you load test it. This script generates a 50 megabyte file of random crap (from /dev/urandom). Everytime it runs it compresses this file with gzip..which is very cpu intensive. It also pings google.com (google always works) to test network connectivity. From there it will log it. If POA gets slow simply take a look in the log and see if the times went way up. If they did, get off the virtual server.
If you are actually serious about using this. I could improve it/add more features to suite POA. Let me know if you need any Linux server help. THere is always a ton of tweaking that can be done...Along with setting up automated database backups offsite..etc.
Excuse my writing/technical explanation of my script. I'm tired and burned out.
