- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Benchmarking
Created by admin on 2008-12-05.
Updated: 2009-07-28, 23:11
We automatically run a quick and dirty benchmarking suite over all our code revisions, in order to detect sudden changes in performance as a result of changes to the code. The resulting charts are available below.
Available charts:
Trunk
- Compilation time - locker_comp
- Compilation time - locker_lib
- Compilation time - quick_comp
- Compilation time - quick_lib
- Compilation time - quick_partest
- Compilation time - quick_plugins
- Compilation time - quick_scalap
- Shootout ackermann (single core)
- Shootout ary (single core)
- Shootout binarytrees (single core)
- Shootout binarytrees.scala-2 (single core)
- Shootout binarytrees.scala-3 (single core)
- Shootout chameneos (single core)
- Shootout except (single core)
- Shootout fannkuch (single core)
- Shootout fannkuch.scala-2 (single core)
- Shootout fibo (single core)
- Shootout harmonic (single core)
- Shootout hash (single core)
- Shootout hash2 (single core)
- Shootout hello (single core)
- Shootout knucleotide.scala-2 (single core)
- Shootout knucleotide.scala-3 (single core)
- Shootout lists (single core)
- Shootout message.scala-2 (single core)
- Shootout nbody.scala-2 (single core)
- Shootout nestedloop (single core)
- Shootout nsieve.scala-2 (single core)
- Shootout nsieve.scala-3 (single core)
- Shootout nsievebits (single core)
- Shootout nsievebits.scala-2 (single core)
- Shootout nsievebits.scala-3 (single core)
- Shootout objinst (single core)
- Shootout partialsums (single core)
- Shootout partialsums.scala-2 (single core)
- Shootout recursive (single core)
- Shootout regexdna (single core)
- Shootout spectralnorm.scala-2 (single core)
- Shootout strcat (single core)
- Shootout sumcol (single core)
- Shootout sumcol.scala-2 (single core)
- Shootout takfp (single core)
Please note: these charts are not to be interpreted as authoritative information concerning the performance of the Scala system. The shootout tests refer to an ancient adaptation of the shootout suite, not comparable to current shootout code. The tests are run on an old box with minimal memory, and are run as a debugging aid only, to detect sudden performance variations.




