Hi,
Jon Tirsen proposed that a nice thing for Goldspike would be to share
the AST's between runtimes, to avoid the huge memory impact and
performance of loading Rails over and over again for a new runtime.
I'm wondering whether this is something we should do. Basically, we
could implement o
Improve JRuby startup time
--
Key: JRUBY-1273
URL: http://jira.codehaus.org/browse/JRUBY-1273
Project: JRuby
Issue Type: Improvement
Components: Core Classes/Modules
Affects Versions: JRuby 1.0.0
Assuming that we can handle the ReturnNode case, I think that this is a
really good idea. Imagine being able to scale better that MRI because JRuby
could share the Rails code.
Java usually gives the impression of having a heavy runtime, but if we can
turn the situation around by cloning the AST an
It would be a decent memory saver I think. The runtime information
getting cached in the AST is the only issue I can think of. This
would probably trim off a meg or two of heap for each addition
instance (the AST is a large memory consumer).
-Tom
On 8/14/07, Ola Bini <[EMAIL PROTECTED]> wrote:
This would be great! :)
Cheers,
Robert
Ola Bini wrote:
Hi,
Jon Tirsen proposed that a nice thing for Goldspike would be to share
the AST's between runtimes, to avoid the huge memory impact and
performance of loading Rails over and over again for a new runtime.
I'm wondering whether this
YAML.dump requires second argument to .respond_to? :write
-
Key: JRUBY-1274
URL: http://jira.codehaus.org/browse/JRUBY-1274
Project: JRuby
Issue Type: Bug
Components: Miscella
Updates:
- case nodes are compiling for most normal cases; "when" with multiple
values doesn't compile just yet.
- valias and undef compile (trivial).
- for loops compile (basically just like calls to "each" with a special
no-scope block).
Charles Oliver Nutter wrote:
Here's a list of the AS
