Difference between revisions of "Testload"

From MosixWiki
Jump to: navigation, search
(New page: TESTLOAD(M1) MOSIX EXTRAS TESTLOAD(M1) '''NAME''' testload - V1.1, MOSIX test program '''SYNOPSIS''' testload [OPTIONS] '...)
(No difference)

Revision as of 17:49, 13 February 2008

TESTLOAD(M1)                     MOSIX EXTRAS                     TESTLOAD(M1)
 
NAME
    testload - V1.1, MOSIX test program
    
SYNOPSIS
    testload [OPTIONS]
  
DESCRIPTION
    A test program that generates artificial load and consumes memory for
    testing the operation of MOSIX.
  
OPTIONS
    -t{seconds} | --time={seconds}
         Run for a given number of CPU seconds: the default is 1800 seconds
         (30 minutes).  A value of 0 causes testload to run indefinitely.
         OR:
    -t{min},{max} | --time={min},{max}
         Run for a random number of seconds between min and max.
    -m{mb}, --mem={mb}
         amount of memory to consume in Megabytes (by default, testload con-
         sumes no significant amount of memory).
    --random-mem
         Fill memory with a random pattern (otherwise, memory is filled with
         the same byte-value).
    --cpu={N}
         When testing pure CPU jobs - perform N units of CPU work, then exit.
         When also doing system-calls (--read, --write, --noiosyscall) - per-
         form N units of CPU work between chunks of system-calls.
    --read[={size}[,{ncalls}[,{repeats}]]
    --write[={size}[,{ncalls}[,{repeats}]]
         perform read OR write system calls of size KiloBytes (default=1KB).
         These calls are repeated in a chunk of ncalls times (default=1024),
         then those chunks are repeated repeats times (default=indefinitely),
         with optional CPU work between chunks if the --cpu option is also
         set.
    --noiosyscall={ncalls}[,{repeats}]
         perform some other system call that does not involve I/O ncalls
         times (default=1024), repeat this {repeats} times (default=indefi-
         nitely), with optional CPU work in between if the --cpu option is
         also set.
    -d, --dir={directory}
    -f, --file={filename}
         select a directory OR a file on which to perform reading or writing
         (the default is to create a file in the /tmp directory).
    --maxiosize={SIZE}
         Once the file size reaches SIZE megabytes, further I/O will resume
         at the beginning of the file.
    -v, --verbose
         produce debug-output.
    --report-migrations
         Report when testload migrates.
    -r, --report
         Produce summary at end of run.
    --sleep SEC
         Sleep for SEC seconds before starting
    -h, --help
         Display a short help screen.
  
EXAMPLES
    testload -t 20
    run CPU for 20 seconds
  
    testload -l 10 -h 20
    runs CPU for a random period of time between 10 and 20 seconds.
   
    testload -f /tmp/20MB --write 32,640,1
    writes 32 KiloBytes of data 640 times (total 20 megabytes) to the file
    /tmp/20MB.
   
    testload -f /tmp/10MB --write 32,640 --maxiosize 10 --cpu=20
    writes 32 KiloBytes of data 640 times (total 20 megabytes) to the file
    /tmp/10MB, alternating this indefinitely with running 20 units of CPU.
    The file "/tmp/10MB" is not allowed to grow beyond 10 MegaBytes: once
    reaching that limit, writing resumes at the beginning of the file.
   
AUTHOR
    Adapted from code by Lior Amar
     
MOSIX                          February 13, 2008                         MOSIX