### poundtime uses between 2 and 4*NUMCPUS threads to hammer on the
### clock_gettime(CLOCK_PROCESS_CPUTIME_ID). This can be an expensive operation
### depending on how the kernel uses locks to calculate it. There are some
### debuggers and applications that monitor their own performance that
### accidentally depend on the performance of this specific call.

# MM Test Parameters
export MMTESTS="poundtime"
export RUN_WARMUP=

# Profiling parameters
export RUN_NOPROFILE=yes
export RUN_FINEPROFILE=no
export RUN_COARSEPROFILE=no
#export OPROFILE_REPORT_ANNOTATE=yes
#export OPROFILE_REPORT_CALLGRAPH=8

# Machine configuration
#export RUN_TUNINGS="$RUN_TUNINGS sysctl"

# Test disk to setup (optional)
#export TESTDISK_RAID_DEVICES=
#export TESTDISK_RAID_MD_DEVICE=/dev/md0
#export TESTDISK_RAID_OFFSET=63
#export TESTDISK_RAID_SIZE=250019532
#export TESTDISK_RAID_TYPE=raid0
#export TESTDISK_PARTITION=/dev/sda6
#export TESTDISK_FILESYSTEM=xfs
#export TESTDISK_MKFS_PARAM="-f -d agcount=8"
#export TESTDISK_MOUNT_ARGS=inode64,delaylog,logbsize=262144,nobarrier

# List of monitors
export RUN_MONITOR=yes
export MONITORS_ALWAYS=
export MONITORS_PLAIN=
export MONITORS_GZIP="proc-vmstat top"
export MONITORS_WITH_LATENCY="vmstat"
export MONITOR_UPDATE_FREQUENCY=10

# poundtime
export POUNDTIME_ITERATIONS=10
export POUNDTIME_MIN_THREADS=2
export POUNDTIME_MAX_THREADS=$((NUMCPUS*4))
