Project

General

Profile

Bug #10003

Hash#fetch performance issue

Added by Richard Schneeman about 2 years ago. Updated about 2 years ago.

Status:
Open
Priority:
Normal
Assignee:
-
ruby -v:
2.1.2
[ruby-core:63477]

Description

It looks like there is a performance issue with Hash#fetch compared to Hash#[]. I found this issue via this gist: https://gist.github.com/jonleighton/3552829. I could not find it reported anywhere on the tracker, forgive me if this is a known issue:

require 'benchmark/ips'

h = { foo: :bar }

Benchmark.ips do |r|
  r.report('#[]')    { h[:foo] }
  r.report('#fetch') { h.fetch(:foo) }
end

Calculating -------------------------------------
                 #[]    124893 i/100ms
              #fetch    121729 i/100ms
-------------------------------------------------
                 #[]  6917857.4 (±20.4%) i/s -   32472180 in   5.008832s
              #fetch  4570251.5 (±18.8%) i/s -   22032949 in   5.015712s

This is in Ruby 2.1.2

History

#1 [ruby-core:63478] Updated by Jeremy Evans about 2 years ago

I believe this is expected since the Hash#[] call is optimized to call rb_hash_aref (see opt_aref in insns.def), where the Hash#fetch call goes through normal method dispatch. Array#[] calls are similarly optimized to call rb_ary_entry.

#2 [ruby-core:63495] Updated by Eric Wong about 2 years ago

Jeremy is correct, Hash# have optimized dispatch.
I hardly see Hash#fetch used anywhere, and optimizing dispatch for
uncommon cases hurts performance of common cases.

P.S. even if Hash#fetch were optimized, it would still be slower
because it has optional args to parse.

Also available in: Atom PDF