From: ko1@...
Date: 2015-03-25T15:27:10+00:00
Subject: [ruby-core:68638] [Ruby trunk - Bug #10999] [PERF]	bm_hash_aref_flo.rb

Issue #10999 has been updated by Koichi Sasada.


Nobuyoshi Nakada wrote:
> It is not a realistic benchmark, that integer parts are all different.

Why? I think it is possible case (I agree not so much case).
Maybe it is issue on Float#hash code.

Adding different (more possible) case is nice, but modifying benchmark and solving issue is not good way. Of course, if benchmark has a bug (not intended behavior), it should be solved.


----------------------------------------
Bug #10999: [PERF] bm_hash_aref_flo.rb
https://bugs.ruby-lang.org/issues/10999#change-51938

* Author: Guo Xiang Tan
* Status: Closed
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: 2.3.0dev (2015-03-18 trunk 49999) [x86_64-linux]
* Backport: 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: REQUIRED
----------------------------------------
Before: 0.066s
After [3bcf9fb53e4b9efabb15a3091fddfb68e5b6fbbe](https://github.com/ruby/ruby/commit/3bcf9fb): 0.094

To view the full graph, please visit http://rubybench.org/ruby/ruby/commits?result_type=hash_aref_flo&display_count=200.

To issue is meant to highlight what we're seeing at RubyBench.org, feel free to close this issue if the trade offs were intended. 



-- 
https://bugs.ruby-lang.org/