bb.util
Class Benchmark.UnitTest

java.lang.Object
  extended by bb.util.Benchmark.UnitTest
Enclosing class:
Benchmark

public static class Benchmark.UnitTest
extends Object

See the Overview page of the project's javadocs for a general description of this unit test class.


Constructor Summary
Benchmark.UnitTest()
           
 
Method Summary
 void benchmark_System_currentTimeMillis()
          Results on 2009-08-27 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_16 server jvm): System.currentTimeMillis: first = 25.889 ns, mean = 21.924 ns (CI deltas: -6.716 ps, +18.038 ps), sd = 322.107 ns (CI deltas: -169.332 ns, +353.907 ns) WARNING: EXECUTION TIMES HAVE EXTREME OUTLIERS, SD VALUES MAY BE INACCURATE
 void benchmark_System_nanoTime()
          Results on 2009-08-27 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_16 server jvm): System.nanoTime: first = 203.424 ns, mean = 199.469 ns (CI deltas: -120.862 ps, +110.777 ps), sd = 1.298 us (CI deltas: -199.032 ns, +286.868 ns) WARNING: execution times have mild outliers, SD VALUES MAY BE INACCURATE
 void test_Benchmark()
          Results on 2009-08-07 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_11 server jvm): Thread.sleep: first = 100.549 ms, mean = 100.575 ms (CI deltas: -31.408 us, +8.119 us), sd = 74.747 us (CI deltas: -72.195 us, +48.902 us) WARNING: EXECUTION TIMES HAVE EXTREME OUTLIERS, execution times may have serial correlation, SD VALUES MAY BE INACCURATE Benchmark correctly measured a known execution time task.
 void test_diagnoseOutliers()
          Results on 2009-04-09 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_11 server jvm): Benchmark correctly detected the following outlier issues: --EXECUTION TIMES APPEAR TO HAVE OUTLIERS --this was determined using the boxplot algorithm with median = 2.565 s, interquantileRange = 458.222 ms --1 are EXTREME (on the low side): #0 = 0.0 s --1 are mild (on the low side): #1 = 1.25 s --1 are EXTREME (on the high side): #59 = 5.0 s --1 are mild (on the high side): #58 = 3.75 s
 void test_diagnoseSerialCorrelation()
          Results on 2009-04-09 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_11 server jvm): Benchmark correctly detected the following serial correlation issues: --EXECUTION TIMES HAVE SERIAL CORRELATION --1 of the 15 autocorrelation function coefficients (r[k]) that were computed are expected to fall outside their 95% CI --but found these 3: r[1] is 3.7109230528011716 sigma above its mean, r[3] is 2.4956492069489786 sigma above its mean, r[4] is 2.2879399503263147 sigma above its mean --the 95% CI for the r[k] was calculated as mean +- 1.96 sigma (i.e. a Gaussian distribution was assumed)
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

Benchmark.UnitTest

public Benchmark.UnitTest()
Method Detail

test_diagnoseOutliers

public void test_diagnoseOutliers()
                           throws Exception
Results on 2009-04-09 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_11 server jvm):

                        Benchmark correctly detected the following outlier issues:
                        --EXECUTION TIMES APPEAR TO HAVE OUTLIERS
                        --this was determined using the boxplot algorithm with median = 2.565 s, interquantileRange = 458.222 ms
                        --1 are EXTREME (on the low side): #0 = 0.0 s
                        --1 are mild (on the low side): #1 = 1.25 s
                        --1 are EXTREME (on the high side): #59 = 5.0 s
                        --1 are mild (on the high side): #58 = 3.75 s
                

Throws:
Exception

test_diagnoseSerialCorrelation

public void test_diagnoseSerialCorrelation()
                                    throws Exception
Results on 2009-04-09 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_11 server jvm):

                        Benchmark correctly detected the following serial correlation issues:
                        --EXECUTION TIMES HAVE SERIAL CORRELATION
                        --1 of the 15 autocorrelation function coefficients (r[k]) that were computed are expected to fall outside their 95% CI
                        --but found these 3: r[1] is 3.7109230528011716 sigma above its mean, r[3] is 2.4956492069489786 sigma above its mean, r[4] is 2.2879399503263147 sigma above its mean
                        --the 95% CI for the r[k] was calculated as mean +- 1.96 sigma (i.e. a Gaussian distribution was assumed)
                

Throws:
Exception

test_Benchmark

public void test_Benchmark()
                    throws Exception
Results on 2009-08-07 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_11 server jvm):

                        Thread.sleep: first = 100.549 ms, mean = 100.575 ms (CI deltas: -31.408 us, +8.119 us), sd = 74.747 us (CI deltas: -72.195 us, +48.902 us) WARNING: EXECUTION TIMES HAVE EXTREME OUTLIERS, execution times may have serial correlation, SD VALUES MAY BE INACCURATE
                        Benchmark correctly measured a known execution time task.
                

Throws:
Exception

benchmark_System_currentTimeMillis

public void benchmark_System_currentTimeMillis()
                                        throws Exception
Results on 2009-08-27 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_16 server jvm):

                        System.currentTimeMillis: first = 25.889 ns, mean = 21.924 ns (CI deltas: -6.716 ps, +18.038 ps), sd = 322.107 ns (CI deltas: -169.332 ns, +353.907 ns) WARNING: EXECUTION TIMES HAVE EXTREME OUTLIERS, SD VALUES MAY BE INACCURATE
                

Throws:
Exception

benchmark_System_nanoTime

public void benchmark_System_nanoTime()
                               throws Exception
Results on 2009-08-27 (2.5 GHz Xeon E5420 desktop, jdk 1.6.0_16 server jvm):

                        System.nanoTime: first = 203.424 ns, mean = 199.469 ns (CI deltas: -120.862 ps, +110.777 ps), sd = 1.298 us (CI deltas: -199.032 ns, +286.868 ns) WARNING: execution times have mild outliers, SD VALUES MAY BE INACCURATE
                

Throws:
Exception