There are many IO operations(database) in mingle test, so the
proportion of improvement is decreased.
From bench_method_dispatch.rb, the improvement is 5-10%. Of course,
it's also a special case.
On the other hand, JRuby use intern to compare to String with "==" in
many places, so the improveme
Ola Bini wrote:
Thomas E Enebo wrote:
I wonder if we cannot do more to try and intern all methods names? If
so then we could do direct == comparison. All method names coming
from parser are intern'd. Also all literal Java strings:
callMethod("foo")
are also intern'd. So the 10,000$ questio
Thomas E Enebo wrote:
I wonder if we cannot do more to try and intern all methods names? If
so then we could do direct == comparison. All method names coming
from parser are intern'd. Also all literal Java strings:
callMethod("foo")
are also intern'd. So the 10,000$ question is where aren't
I wonder if we cannot do more to try and intern all methods names? If
so then we could do direct == comparison. All method names coming
from parser are intern'd. Also all literal Java strings:
callMethod("foo")
are also intern'd. So the 10,000$ question is where aren't we
interning? Could i
dreamhead wrote:
Hi!
This is dreamhead (one of core developers from XRuby) from
ThoughtWorks. I have been working on JRuby performance recently. I
just add RubyID into JRuby which is helpful to performance in XRuby.
RubyID is similar ID(long) in MRI which use ID to replace String to
reduce compa
Hi!
This is dreamhead (one of core developers from XRuby) from
ThoughtWorks. I have been working on JRuby performance recently. I
just add RubyID into JRuby which is helpful to performance in XRuby.
RubyID is similar ID(long) in MRI which use ID to replace String to
reduce comparison cost.
id.tx
