diff options
author | Performant Data LLC <performantdata@users.noreply.github.com> | 2016-03-23 12:07:00 -0700 |
---|---|---|
committer | Performant Data LLC <performantdata@users.noreply.github.com> | 2016-05-03 11:46:57 -0700 |
commit | e1b58ccafc598c06b8011e3e0f411f6e91b99353 (patch) | |
tree | ff54d1bd62e0c1e125a407d5ea6e673f687d7cd4 /test/benchmarks/build.sbt | |
parent | 303130b81599528db35d9612fff42cf7e570e15a (diff) | |
download | scala-e1b58ccafc598c06b8011e3e0f411f6e91b99353.tar.gz scala-e1b58ccafc598c06b8011e3e0f411f6e91b99353.tar.bz2 scala-e1b58ccafc598c06b8011e3e0f411f6e91b99353.zip |
Add get() tests to OpenHashMap, reduce timing artifacts.
In order to get a better exploration of the variance of tests in a
limited time, I've reduced the number of measurement iterations and
increased the number of forks. By sight, the measurement iterations
seemed pretty consistent within a trial, whereas they would vary
widely on occasional forks.
I extended testing down to 50-entry maps, to explore the rise in
service times that I was seeing at small scale. This is probably a
timing artifact, from too-short invocations, since I'm using
@Level.Invocation in the put() tests. To fix that, I enlarged the
unit of testing, by creating multiple, sometimes thousands, of maps
for the invocation to fill. This has also changed the test from
filling a previously-filled map, to filling a new, but sufficiently
sized map. The put()/remove() test now performs much worse (on a
more realistic scenario).
This also adds a couple tests for calling get() against a map that's
been filled only with put()s, or with a mix of put() and remove().
Diffstat (limited to 'test/benchmarks/build.sbt')
0 files changed, 0 insertions, 0 deletions