This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 114666

Summary:	Speed up startup of JRuby
Product:	ruby	Reporter:	nicksieger <nicksieger>
Component:	Platform	Assignee:	issues@ruby <issues>
Status:	NEW ---
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description nicksieger 2007-09-04 17:13:22 UTC

When I launch a test (Run -> Run File... -> Test "my_test.rb"), the time taken to launch the test is too great.  The
test itself usually run in subsecond speeds, but the launching process seems to take a fair amount longer.  It would be
great if the time to complete the test, including launch, was under a second.  I find my attention shifting away from
the editor and to other tasks because I don't get feedback quickly enough.

A secondary issue is that, once the test is launched, the Window -> Editor shortcut (command-0 on mac) doesn't work for
jumping back to the editor pane.  Jumping to the project pane first (command-1) and then to the editor pane does seem to
work.

Comment 1 nicksieger 2007-09-04 17:26:14 UTC

BTW, I'm using build 070814.

Comment 2 Torbjorn Norbye 2007-10-15 23:20:26 UTC

I assume you are using JRuby as your interpreter?  JRuby is launched as a separate process for each test, which is why
there's such as delay - it's JRuby startup cost every time. If you switch to C Ruby it's nearly instant.  I'm not sure
what I can do about this. We have the same problem with running the Rails "Generate" script - there's a noticeable pause
each time you run it as JRuby warms up. I spoke briefly with Ola at JavaOne about this - perhaps we could run some sort
of JRuby server process which handles Ruby execution requests directly. The difficulty there is with getting the output
for each request sorted out.

Regarding your focus issues, I can't reproduce that -- hitting Command-F6 doesn't shift the focus to the output window
for me. Perhaps this was previous behavior which is now fixed? Even command-dot to navigate through the error messages
in the output window keeps the focus in the editor.

Marking issue as "future" since I can't address the JRuby-startup issue here. Hopefully the autotest integration (where
JRuby is left running) makes this less of a problem?

Comment 3 Erno Mononen 2008-08-27 13:11:36 UTC

Reassigning to ruby/platform, where the JRuby startup issue should be handled (if there is something we can do for that 
in NetBeans). The second issue seems to be fixed, maybe it was some temporary problem.

Comment 4 Martin Krauskopf 2008-08-27 13:20:37 UTC

I'm changing the subject to be a little general. Might be too much, since I'm not sure about the best solution. At
present the most right solution seems to be to utilize Nailgun or at least, in the beginning, to provide some
help/option for the users who wants to utilize it.