From: "Юрий Соколов" Date: 2015-08-11T22:17:16+03:00 Subject: [ruby-core:70338] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI --f46d0435c06a487946051d0df31f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Eric Wong, you should measure, not expect. With current implementation, lookup performance really matters. Does Github still use patch with per class method cache instead of global one? 11 =D0=B0=D0=B2=D0=B3. 2015 =D0=B3. 21:26 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0= =BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Eric Wong" =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > Nice. Thank you guys for looking into this. > > I prefer smallest size. With inline cache, global method cache and tiny > tables; I expect lookup algorithm performance is not too important. > --f46d0435c06a487946051d0df31f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Eric Wong, you should measure,=C2=A0 not expect. With curren= t implementation, lookup performance really matters.

Does Github still use patch with per class method cache inst= ead of global one?

11 =D0=B0=D0=B2=D0=B3. 2015 =D0=B3. 21:26 =D0=BF= =D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Er= ic Wong" <normalperson@yhb= t.net> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
Nice.=C2=A0 Thank you guys for lookin= g into this.

I prefer smallest size.=C2=A0 With inline cache, global method cache and ti= ny
tables; I expect lookup algorithm performance is not too important.
--f46d0435c06a487946051d0df31f--