Issue #10650 has been updated by mame (Yusuke Endoh).

Status changed from Open to Closed

The benchmark has been greatly improved (about 3 times) since this ticket was open.  So I close this ticket.

Still, it might be worth investigating the commits in question, but unfortunately, there is no one who is willing to do.  If anyone is interested, the contribution is welcome.

----------------------------------------
Bug #10650: [PERF] bm_hash_keys and  bm_hash_values
https://bugs.ruby-lang.org/issues/10650#change-83175

* Author: tgxworld (Guo Xiang Tan)
* Status: Closed
* Priority: Normal
* Assignee: nobu (Nobuyoshi Nakada)
* Target version: 
* ruby -v: Trunk
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
Hi!

Benchmarks bm_hash_keys and bm_hash_values seemed to have gotten slower after a commit between [e23d1736797f9b7170c80a7470b8e5cecd308105](https://github.com/ruby/ruby/commit/e23d1736797f9b7170c80a7470b8e5cecd308105) and [c73c34e27f028b6bcada9e5cd9a2961a822fc813](https://github.com/ruby/ruby/commit/c73c34e27f028b6bcada9e5cd9a2961a822fc813).

You may view the benchmark result graphs at [https://railsbench.herokuapp.com/tgxworld/ruby?utf8=%E2%9C%93&result_types%5B%5D=hash_keys&result_types%5B%5D=hash_values&commit=Submit](https://railsbench.herokuapp.com/tgxworld/ruby?utf8=%E2%9C%93&result_types%5B%5D=hash_keys&result_types%5B%5D=hash_values&commit=Submit).

On my builder, it is roughly 10%-11% slower. Not sure if the results are significant but I wish to bring it up. Thanks in advance!



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

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>