It is currently Wed Jul 30, 2014 1:16 pm

All times are UTC - 8 hours




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 6 posts ] 
Author Message
 Post subject: Integration of stress
PostPosted: Wed Jul 18, 2007 6:04 am 
Offline

Joined: Wed Jul 18, 2007 5:48 am
Posts: 3
Location: Germany
Hi there!

First of all: great work!
I stumbled upon UBCD several years ago and still love using it!

The main point is, that I found a nice tool for stress-testing a complete system:

Stress
From http://weather.ou.edu/~apw/projects/stress/
stress is a simple tool that imposes a configurable amount of CPU, memory, I/O, and disk stress on POSIX-compliant operating systems. It is written in portable ANSI C and uses the GNU Autotools to compile on most UNIX-like operating systems. It is free software, licensed under the GNU GPL.


The company I'm currently working for is using this tool for stress-testing hardware before shipping, as it this tool imposes load an the whole system and not just the CPU.

Is there a possibility that this tool will be included in one of the next UBCD releases?

Best wishes,
Holger


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jul 18, 2007 7:09 am 
Offline

Joined: Fri Sep 23, 2005 1:21 am
Posts: 336
Location: France
Well if it is free and since, as far as I know, there are not already tools that do the same thing, I don't see why it would not be added sooner or later :)

_________________
Hammerite Compendium of Precepts, Regimens and Rules of Conduct, Vol. 113 :
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jul 20, 2007 3:12 am 
Offline

Joined: Mon Feb 21, 2005 10:59 pm
Posts: 1274
Since this is a Unix app, it would be best if someone could supply me with a boot disk containing the app, or better still, integrate it into Adrian's Linux boot disk that already contains mprime and stresscpu.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Aug 03, 2007 4:10 am 
Offline

Joined: Wed Jul 18, 2007 5:48 am
Posts: 3
Location: Germany
I'd be willing to take the integration work!

As I'm not involved in your "workflow", how would this have to work out?

I'd prefer an integration in Adrian's disk, as stress should *imho* work well with his disk.

Am I to contact him?

All the best,
Holger


Top
 Profile  
 
 Post subject:
PostPosted: Sun Aug 05, 2007 5:15 am 
Offline

Joined: Mon Feb 21, 2005 10:59 pm
Posts: 1274
I think you should just work on the existing image and email it to me.

Adrian's got a new job and is real busy, so I don't think he will be able to get involved.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Aug 06, 2007 5:26 am 
Offline

Joined: Wed Jul 18, 2007 5:48 am
Posts: 3
Location: Germany
Work is done - the whole thing is currently "burning" a laptop sitting next to me ;-)

Steps I've taken:

I had to create a new image, as Adrian's had not enough space left to include stress.

Well, the new image is basically just the same as the old, besides that it is 500kb larger and now contains stress, sitting in /usr/bin, just like the rest of the burn-in-tools.

Modified linuxrc
It just includes one more case (stress) for starting "stress".

Code:
stress)
   echo "Starting /usr/bin/stress"
   /usr/bin/stress --help
   echo "Please start /usr/bin/stress with appropriate settings"
   ;;


Attention:
stress does not come up with a burn-in-test itself, but with the help-menu - that's the --help parameter!

It hast to be started manually, as there are different parameters (cpu/io/...) to chose from - I did not want to be the one in charge for deciding which combination is the best stress-test ;-)

Another thing I noticed when modifying linuxrc, was a call to cpuburn-in after the closing esac in the linuxrc-script:

Code:
/cpuburn-in 10080


I commented it out, as it looks like a legacy line from a much older version of this script.

The correct menu.lst entry for grub is - new image is named scburn.gz at the moment - but feel free to change this:
Code:
title stress - a system burn-in test
   kernel /dists/ubcd/boot/cpustres ubcd=stress ramdisk_size=9000
   initrd /boot/scburn.gz



Corresponding isolinux-entry:
Code:
LABEL stress
  MENU LABEL stress - a system burn-in test
        KERNEL /boot/cpustres
        APPEND initrd=/boot/scburn.gz ubcd=stress ramdisk_size=9000



One last thing:
I stumbled across a bug while booting some of the stuff in the old cpustres-image.
Code:
attemp to access beyond end of device
01:00: rw=0, want=8406, limit=4096
...

This only occured with two out of four test setups.

This was fixable by using the following boot-options:
Code:
"ramdisk_size=8500"
in the old and
Code:
"ramdisk_size=9000"
in the new image - you can also see this in the menu.lst-enty or the isolinux-entry.

Well, that's it for now :D

Victor: I'll send you the new image in some minutes, after I got me some fresh coffee :-)

I'd be glad if you could give me some feedback if the stuff is "okay" so far and if it will be included in one of the next releases.

Best wishes,
Holger


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 6 posts ] 

All times are UTC - 8 hours


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group