Isolation
Download resources for the Isolation Benchmark Suite

Isolation Benchmark Suite Releases

The files in each stress test directory should include:

cpu/memory/fork/disk_iozone/network/
Makefile
cpuBomb.c
README
 Makefile
mallocBomb.c
malloc.sh
README		 forkBomb.c
Makefile
README		 iozone-3.257/
Makefile
run_iozone.sh
README		 Makefile
bin
perl
src
stress.sh
x.txt
README
Some header files and error codes are different between Solaris and Linux:
  1. Memory stress test uses calloc() to allocate memory. When the memory is used up then the stress tess will print an error.

    For the Solaris version, mallocBomb.c includes the extra header files:
     <sys/types.h>, <unistd.h>, <errno.h>, <limits.h>.
    If allocating memory fails, the Linux version returns NULL, but the Solaris version could return two error codes: 
    ENOMEM     The physical limits of the system are exceeded by
           size bytes of memory which cannot be allocated.

EAGAIN     There is not enough memory available to allocate
           size bytes of memory; but the application could
           try again later
  2. Disk I/O stress test uses IOzone benchmark tool to read from and write to the disk.

    IOzone should be compiled for the operating systme and archicture that you are running on. 
    make <target> (example targets: linux, Solaris10gcc)
Results from running the Isolation Benchmark Suite
  • Coming Soon.


Publications