Hi.
The big problem with ObjectSpace seems to be that it punishes even those
who aren't using it in the current implementation. If we changed the
implementation to something like this:
private List references = new ArrayList();
private Set realReferences = null;
private ReferenceQueue
Hi,
Time for a new update on the YAML front. I've rewritten the parser in
Java. (VERY inefficient Java, I have to add. It's really naive right
now, actually).
The test case for RbYAML give this output:
D:\Project\rbyaml\testruby test_time_events.rb yaml\gems2.yml
loading a file 100 times took
Testing, please ignore.
___
Jruby-devel mailing list
Jruby-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jruby-devel
Hi,
Time for a new update on the YAML front. I've rewritten the parser in
Java. (VERY inefficient Java, I have to add. It's really naive right
now, actually).
The test case for RbYAML give this output:
D:\Project\rbyaml\testruby test_time_events.rb yaml\gems2.yml
loading a file 100 times took
This seems to have gotten lost while SF mail was down yesterday *shakes fist at SF*-- Forwarded message --From: Charles O Nutter
[EMAIL PROTECTED]Date: Jun 4, 2006 4:17 PMSubject: More performance numbers and a committable patchTo: jruby-devel@lists.sourceforge.net
ObjectSpace is
Blast, forgot the patch.On 6/4/06, Charles O Nutter [EMAIL PROTECTED] wrote:
ObjectSpace is slow.I'm optimizing RubyString and seeing again and again how slow OS makes object creation. I've attached a patch that doesn't break anything and optimizes a few aspects of RubyString. Without OS enabled,
ObjectSpace is slow.I'm optimizing RubyString and seeing again and again how slow OS makes object creation. I've attached a patch that doesn't break anything and optimizes a few aspects of RubyString. Without OS enabled, this patch gives 15-20% improvement in the given microbenchmark. It's not
