On Tue, 11 Apr 2006, Ola Bini defenestrated me: > Hello again. > > With the major performance improvements in RubyString due to Thom's > StringBuffer implementation the next stopgap have been fixed. JRuby just > wooshed through 126k lines in less than a minute doing regexps and regexp > subs on each line. VERY nice. (Just think what we could do with thread > unsafe StringBuilder from Tiger instead...) > > But anyway, next problem: YAML. > It seems 126k lines of YAML definition is to much for our poor Ruby > implementation of it. It dies with an OutOfMemoryError. > So my thinking is this: is there anyone who knows anything about the > current implementation? As far as I can find out, it depends quite heavily > on Racc-stuff. A first way to get this working would be to just do a > straightforward Ruby-to-Java translation of yaml.rb, but this is > problematic due to the Racc-stuff. So, any leads here?
Did you try raising heap options in Java? Hardly a nice solution, but it would be nice to know the upper boounds on memory. The other thought could be a memory leak? Who knows...maybe we are holding a reference somewhere and not releasing something? The JYaml thread does seem like a more long-term solution, but it would be nice to figure out if this is a leak or not. -Tom -- + http://www.tc.umn.edu/~enebo +---- mailto:[EMAIL PROTECTED] ----+ | Thomas E Enebo, Protagonist | "Luck favors the prepared | | | mind." -Louis Pasteur | ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
