undefined | Better HN

0 pointsConfusion15y ago0 comments

The second is actually much less painful than people generally think. Jruby -e 'some code' only takes half a second on my machine, which is fast enough to not be a problem. The main slowness people experience has to do with loading gems, usually via rubygems. That is painfully slow, but does not have anything to do with JVM startup time.

0 comments

tptacek15y ago

"jruby -e 1", cold start, just took 4 seconds for me. I use jruby interactively almost every day (it's extremely handy in penetration testing), and I'm pretty sure jruby is noticeably slower to start than MRI.

ConfusionOP15y ago

It's definitely noticably slower, but 4 seconds per startup would make it unusable for me. However, since it's

  time jruby -e 1
  real	0m0.514s
  user	0m0.510s
  sys	0m0.040s

I find it acceptable (could it be the SSD in my laptop that makes such a large difference?). As http://jira.codehaus.org/browse/JRUBY-5181 shows, as soon as some gems come into the picture, actual startup times deteriorate rapidly.

tptacek15y ago

I'm not an SSD, but mine was also a cold start; are you sure yours wasn't already cached?

1 more reply

j / k navigate · click thread line to collapse

0 pointsConfusion15y ago0 comments

0 comments

tptacek15y ago

ConfusionOP15y ago

It's definitely noticably slower, but 4 seconds per startup would make it unusable for me. However, since it's

  time jruby -e 1
  real	0m0.514s
  user	0m0.510s
  sys	0m0.040s

tptacek15y ago

I'm not an SSD, but mine was also a cold start; are you sure yours wasn't already cached?

1 more reply

j / k navigate · click thread line to collapse