"Fossies" - the Fresh Open Source Software Archive

Member "stress-ng-0.09.56/example-jobs/interrupt.job" (15 Mar 2019, 7516 Bytes) of package /linux/privat/stress-ng-0.09.56.tar.xz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 #
    2 # interrupt class stressors:
    3 #   various options have been commented out, one can remove the
    4 #   proceeding comment to enable these options if required.
    5 
    6 #
    7 # run the following tests in parallel or sequentially
    8 #
    9 run sequential
   10 # run parallel
   11 
   12 #
   13 # aggressive:
   14 #   enables more file, cache and memory aggressive options. This may
   15 #   slow tests down, increase latencies and  reduce  the  number  of
   16 #   bogo  ops as well as changing the balance of user time vs system
   17 #   time used depending on the type of stressor being used.
   18 #
   19 # aggressive
   20 
   21 #
   22 # ignite-cpu:
   23 #   alter kernel controls to try and maximize the CPU. This requires
   24 #   root  privilege  to alter various /sys interface controls.  Cur‐
   25 #   rently this only works for Intel P-State enabled x86 systems  on
   26 #   Linux.
   27 #
   28 # ignite-cpu
   29 
   30 #
   31 # keep-name:
   32 #   by  default,  stress-ng  will  attempt to change the name of the
   33 #   stress processes according to their functionality;  this  option
   34 #   disables  this and keeps the process names to be the name of the
   35 #   parent process, that is, stress-ng.
   36 #
   37 # keep-name
   38 
   39 #
   40 # metrics-brief:
   41 #   enable metrics and only output metrics that are non-zero.
   42 #
   43 metrics-brief
   44 
   45 #
   46 # verbose
   47 #   show all debug, warnings and normal information output.
   48 #
   49 verbose
   50 
   51 #
   52 # run each of the tests for 60 seconds
   53 #  stop stress test after N seconds. One can also specify the units
   54 #  of time in seconds, minutes, hours, days or years with the  suf‐
   55 #  fix s, m, h, d or y.
   56 #
   57 timeout 60s
   58 
   59 #
   60 # per stressor options start here
   61 #
   62 
   63 #
   64 # aio stressor options:
   65 #   start  N  workers  that  issue  multiple  small asynchronous I/O
   66 #   writes and reads on a relatively small temporary file using  the
   67 #   POSIX  aio  interface.  This will just hit the file system cache
   68 #   and soak up a lot of user and kernel time in  issuing  and  han‐
   69 #   dling I/O requests.  By default, each worker process will handle
   70 #   16 concurrent I/O requests.
   71 #
   72 aio 0			# 0 means 1 stressor per CPU
   73 # aio-ops 1000000	# stop after 1000000 bogo ops
   74 # aio-requests 16	# I/O requests per aio operation
   75 
   76 #
   77 # aiol stressor options:
   78 #   start N workers that issue multiple 4K random  asynchronous  I/O
   79 #   writes  using  the  Linux  aio system calls io_setup(2), io_sub‐
   80 #   mit(2), io_getevents(2) and  io_destroy(2).   By  default,  each
   81 #   worker process will handle 16 concurrent I/O requests.
   82 #
   83 aiol 0			# 0 means 1 stressor per CPU
   84 # aiol-ops 1000000	# stop after 1000000 bogo ops
   85 # aiol-requests 16	# I/O requests per aio operation
   86 
   87 #
   88 # clock stressor options:
   89 #   start N workers exercising clocks  and  POSIX  timers.  For  all
   90 #   known clock types this will exercise clock_getres(2), clock_get‐
   91 #   time(2) and clock_nanosleep(2).  For all known  timers  it  will
   92 #   create  a  50000ns  timer  and  busy poll this until it expires.
   93 #   This stressor will cause frequent context switching.
   94 #
   95 clock 0			# 0 means 1 stressor per CPU
   96 # clock-ops 1000000	# stop after 1000000 bogo ops
   97 
   98 #
   99 # fault stressor options:
  100 #   start N workers that generates minor and major page faults.
  101 #
  102 fault 0			# 0 means 1 stressor per CPU
  103 # fault-ops 1000000	# stop after 1000000 bogo ops
  104 
  105 #
  106 # itimer stressor options:
  107 #   start N workers that exercise the system interval  timers.  This
  108 #   sets  up  an ITIMER_PROF itimer that generates a SIGPROF signal.
  109 #   The default frequency for the itimer  is  1  MHz,  however,  the
  110 #   Linux kernel will set this to be no more that the jiffy setting,
  111 #   hence high frequency SIGPROF signals are not normally  possible.
  112 #   A busy loop spins on getitimer(2) calls to consume CPU and hence
  113 #   decrement the itimer based on amount of time spent  in  CPU  and
  114 #   system time.
  115 #
  116 itimer 0		# 0 means 1 stressor per CPU
  117 # itimer-ops 1000000	# stop after 1000000 bogo ops
  118 # itimer-freq 750	# 750 Hz timer clock
  119 
  120 #
  121 # kill stressor options:
  122 #   start N workers sending SIGUSR1 kill signals to a SIG_IGN signal
  123 #   handler. Most of the process time will end up in kernel space.
  124 #
  125 kill 0			# 0 means 1 stressor per CPU
  126 # kill-ops 1000000	# stop after 1000000 bogo ops
  127 
  128 #
  129 # schedpolicy stressor options:
  130 #   start N workers that work set the worker  to  various  available
  131 #   scheduling policies out of SCHED_OTHER, SCHED_BATCH, SCHED_IDLE,
  132 #   SCHED_FIFO and SCHED_RR.  For the real time scheduling  policies
  133 #   a random sched priority is selected between the minimum and max‐
  134 #   imum scheduling prority settings.
  135 #
  136 schedpolicy 0		# 0 means 1 stressor per CPU
  137 # schedpolicy-ops 1000000 # stop after 1000000 bogo ops
  138 
  139 #
  140 # sigfd stressor options:
  141 #   start  N  workers that generate SIGRT signals and are handled by
  142 #   reads by a child process using a file descriptor  set  up  using
  143 #   signalfd(2).   (Linux  only). This will generate a heavy context
  144 #   switch load when all CPUs are fully loaded.
  145 #
  146 sigfd 0			# 0 means 1 stressor per CPU
  147 # sigfd-ops 1000000	# stop after 1000000 bogo ops
  148 
  149 #
  150 # sigfpe stressor options:
  151 #   start N workers that  rapidly  cause  division  by  zero  SIGFPE
  152 #   faults.
  153 #
  154 sigfpe 0		# 0 means 1 stressor per CPU
  155 # sigfpe-ops 1000000	# stop after 1000000 bogo ops
  156 
  157 #
  158 # sigpending stressor options:
  159 #   start  N workers that check if SIGUSR1 signals are pending. This
  160 #   stressor masks SIGUSR1, generates a SIGUSR1 signal and uses sig‐
  161 #   pending(2)  to see if the signal is pending. Then it unmasks the
  162 #   signal and checks if the signal is no longer pending.
  163 #
  164 sigpending 0		# 0 means 1 stressor per CPU
  165 # sigpending-ops 1000000 # stop after 1000000 bogo ops
  166 
  167 #
  168 # sigq stressor options:
  169 #   start   N  workers  that  rapidly  send  SIGUSR1  signals  using
  170 #   sigqueue(3) to child processes that wait for the signal via sig‐
  171 #   waitinfo(2).
  172 #
  173 sigq 0			# 0 means 1 stressor per CPU
  174 # sigq-ops 1000000	# stop after 1000000 bogo ops
  175 
  176 #
  177 # sigsegv stressor options:
  178 #   start  N  workers  that  rapidly  create  and catch segmentation
  179 #   faults.
  180 #
  181 sigsegv 0		# 0 means 1 stressor per CPU
  182 # sigsegv-ops 1000000	# stop after 1000000 bogo ops
  183 
  184 #
  185 # sigsuspend stressor options:
  186 #   start N workers that each spawn off 4 child processes that  wait
  187 #   for  a  SIGUSR1  signal from the parent using sigsuspend(2). The
  188 #   parent sends SIGUSR1 signals to each child in rapid  succession.
  189 #   Each sigsuspend wakeup is counted as one bogo operation.
  190 #
  191 sigsuspend 0		# 0 means 1 stressor per CPU
  192 # sigsuspend-ops 1000000 # stop after 1000000 bogo ops
  193 
  194 #
  195 # sleep stressor options:
  196 #   start  N  workers that spawn off multiple threads that each per‐
  197 #   form multiple sleeps of ranges 1us to 0.1s.  This creates multi‐
  198 #   ple context switches and timer interrupts.
  199 #
  200 sleep 0			# 0 means 1 stressor per CPU
  201 # sleep-ops 1000000	# stop after 1000000 bogo ops
  202 # sleep-max 1024	# start 1024 threads per sleep stressor
  203 
  204 #
  205 # timer stressor options:
  206 #   stop  timer  stress  workers  after  N  bogo timer events (Linux
  207 #   only).
  208 #
  209 timer 0			# 0 means 1 stressor per CPU
  210 # timer-ops 1000000	# stop after 1000000 bogo ops
  211 # timer-freq 8000	# 8000 Hz timer frequency
  212 # timer-rand		# enable some timer jitter
  213 
  214 #
  215 # timerfd stressor options:
  216 #   start N workers creating timerfd events at a default rate  of  1
  217 #   MHz  (Linux  only);  this  can  create a many thousands of timer
  218 #   clock events. Timer events are waited  for  on  the  timer  file
  219 #   descriptor  using  select(2) and then read and counted as a bogo
  220 #   timerfd op.
  221 #
  222 timerfd 0		# 0 means 1 stressor per CPU
  223 # timerfd-ops 1000000	# stop after 1000000 bogo ops
  224 # timerfd-freq 8000	# 8000 Hz timefd frequency
  225 # timerfd-rand		# enable some timer jitter