# Sample configuration for testing the sorting of different list implementations

# Uncomment this property to set the number of times to run each task
# (default is 5)
# jbench.runs=5


# Uncoment this property to use the JVM profiling API to get more
# accurate timing information. See the documentation for more
# details on how to install and use the required native library.
jbench.timer=cpu


# Uncomment this property if you use the CPU timer on Linux and see
# results which appear to be 1000 times shorter than they should be -
# I believe there is a bug in some implementations of the HotSpot
# JVMPI which report microseconds rather than nanoseconds
# jbench.timer.scale=1000


# Uncomment this property if you wish JBench to abort its entire
# benchmark if any tasks fail the configuration phase
# jbench.failfast=true


# Uncomment this property to write to a log file instead of System.out
# jbench.log=filename.log


# Uncomment this property to overwrite (rather than append) to the
# log file (makes no difference if writing to System.out)
# jbench.log.append=false


# Uncomment this property to change how many of the worst results to
# exclude from the statistics (default is 1)
# jbench.stats.excludeworst=1


# Uncomment this property to change how many of the best results to
# exclude from the statistics (default is 1)
# jbench.stats.excludebest=1


# Uncomment this property to change what system information is
# displayed. The information is listed in the order given in
# the property. The default is vm, os, clock. Valid items are:
#
# vmspec: virtual machine specification
# vm: virtual machine implementation
# os: operating system
# jrespec: runtime environment specification
# jre: runtime environment implementation
# timer: timer type and granularity
# jbench.sysinfo=vm, os, timer

# Use the uk.org.skeet.jbench.tasks package to find classes.
# This property is a comma-separated list of packages - in
# fact it's *really* just a list of prefixes - JBench adds '.' to the
# end if there isn't one already there, so you *can* think of
# it as a list of packages.
# (The unnamed package is always available, so you can
# always just specify the full class name.)
jbench.packages=uk.org.skeet.jbench.tasks

# Example uses of the demonstration ListSort task

# Both tasks should use the same size
# Note that this can also be represented (as can any integer
# parameters) in a locale-specific way (for the system locale)
# eg global.size=1,000,000
global.size = 100000


# Tell JBench which class to use - every task definition needs
# a line like this
task.1.class = ListSort

# Tell the ListSort task which type of List to sort
task.1.type = java.util.ArrayList


# And similarly for the second task definition...
task.2.class = ListSort
task.2.type = java.util.Vector
