home.social

#truffleruby — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #truffleruby, aggregated by home.social.

  1. Ah, #TruffleRuby, the lovechild of an #Oracle internship and a decade-long #PhD ✨. Because nothing screams "cutting-edge" like languishing in academic obscurity until the almighty #Shopify swoops in to sprinkle some e-commerce magic dust 💸. But hey, at least it can outrun JRuby—because that's what we were all waiting for, right? 😏
    chrisseaton.com/truffleruby/ #eCommerce #JRuby #HackerNews #ngated

  2. @headius it has been ages that I stumbled over a different handling between #MRI and #JRuby but today it has happened. 😉

    EDIT: nevermind. I converted the references but I'm still open to feedback if you have any.

    I'm surely doing something wrong, so I'm open in case you have any advice for me.

    github.com/rails/marcel/action

    #TruffleRuby is affected too.

  3. Ah, nothing like posting on #StackOverflow to toughen up one's sense of self! I typically only answer the tricky questions there, so dealing with criticism of minor oversights, off-by-ones, and conversion errors are part of the fun. Ever try converting µs to femtoseconds when #benchmarking iterations on large data sets? Less fun than you think!

    On the other hand, #TruffleRuby for the performance win. 900% faster for this use case than #CRuby, even with #YJIT.

    stackoverflow.com/a/78263220/1

  4. Ah, nothing like posting on #StackOverflow to toughen up one's sense of self! I typically only answer the tricky questions there, so dealing with criticism of minor oversights, off-by-ones, and conversion errors are part of the fun. Ever try converting µs to femtoseconds when #benchmarking iterations on large data sets? Less fun than you think!

    On the other hand, #TruffleRuby for the performance win. 900% faster for this use case than #CRuby, even with #YJIT.

    stackoverflow.com/a/78263220/1

  5. Ah, nothing like posting on #StackOverflow to toughen up one's sense of self! I typically only answer the tricky questions there, so dealing with criticism of minor oversights, off-by-ones, and conversion errors are part of the fun. Ever try converting µs to femtoseconds when #benchmarking iterations on large data sets? Less fun than you think!

    On the other hand, #TruffleRuby for the performance win. 900% faster for this use case than #CRuby, even with #YJIT.

    stackoverflow.com/a/78263220/1

  6. @ervan Without changing your actual #RSpec or #CI setup, you can create multiple #Rake tasks to run specific tags or spec files. Then use #gnuparallel (or `parallel` from #moreutils) to run the tasks on multiple CPUs or cores. For GNU, see the `-j`, `--use-cores-instead-of-threads`, and `--use-sockets-instead-of-threads` flags.

    You can also use subshells or background tasks for OS allocation in #bash, #zsh, or #fish. Also, consider threading without a GIL on #TruffleRuby.

  7. @ruby_discussions As much as I dislike promoting anything #Java or Oracle related, I have to say that a lot of my #RubyLang code (so long as it doesn't require forking) runs ~1 gazillion times faster on #TruffleRuby than #CRuby even with #YJIT enabled. It's now my default for certain types of performance-oriented code, especially for threading.

  8. @ruby_discussions As much as I dislike promoting anything #Java or Oracle related, I have to say that a lot of my #RubyLang code (so long as it doesn't require forking) runs ~1 gazillion times faster on #TruffleRuby than #CRuby even with #YJIT enabled. It's now my default for certain types of performance-oriented code, especially for threading.

  9. @ruby_discussions As much as I dislike promoting anything #Java or Oracle related, I have to say that a lot of my #RubyLang code (so long as it doesn't require forking) runs ~1 gazillion times faster on #TruffleRuby than #CRuby even with #YJIT enabled. It's now my default for certain types of performance-oriented code, especially for threading.

  10. @ruby_discussions As much as I dislike promoting anything #Java or Oracle related, I have to say that a lot of my #RubyLang code (so long as it doesn't require forking) runs ~1 gazillion times faster on #TruffleRuby than #CRuby even with #YJIT enabled. It's now my default for certain types of performance-oriented code, especially for threading.

  11. @ruby_discussions As much as I dislike promoting anything #Java or Oracle related, I have to say that a lot of my #RubyLang code (so long as it doesn't require forking) runs ~1 gazillion times faster on #TruffleRuby than #CRuby even with #YJIT enabled. It's now my default for certain types of performance-oriented code, especially for threading.