There are three ways to install TruffleRuby:
bin/rubycommand that runs TruffleRuby. We recommend that you use a Ruby manager to use TruffleRuby inside GraalVM.
Via your Ruby manager/installer (RVM, rbenv, chruby, ruby-build, ruby-install). This contains only TruffleRuby, in the native configuration, making it a smaller download. It is meant for users just wanting a Ruby implementation and already using a Ruby manager.
language: ruby rvm: - truffleruby
You can use
gem to install Gems as normal.
Please report any issue you might find on GitHub.
TruffleRuby aims to:
- Run idiomatic Ruby code faster
- Run Ruby code in parallel
- Boot Ruby applications in less time
- Execute C extensions in a managed environment
- Provide new tooling such as debuggers and monitoring
- All while maintaining very high compatibility with the standard implementation of Ruby
There are two main configurations of TruffleRuby: native and JVM. It's important to understand the different configurations of TruffleRuby, as each has different capabilities and performance characteristics. You should pick the execution mode that is appropriate for your application.
TruffleRuby by default runs in the native configuration. In this
configuration, TruffleRuby is ahead-of-time compiled to a standalone native
executable. This means that you don't need a JVM installed on your system to
use it. The advantage of the native configuration is that it starts about as
fast as MRI, it may use less memory, and it becomes fast in less time. The
disadvantage of the native configuration is that you can't use Java tools like
VisualVM, you can't use Java interoperability, and peak performance may be
lower than on the JVM. The native configuration is used by default, but you
can also request it using
--native. To use polyglot programming with the
native configuration, you need to use the
--polyglot flag. To check you
are using the native configuration,
ruby --version should mention
TruffleRuby can also be used in the JVM configuration, where it runs as a
normal Java application on the JVM, as any other Java application would. The
advantage of the JVM configuration is that you can use Java interoperability,
and peak performance may be higher than the native configuration. The
disadvantage of the JVM configuration is that it takes much longer to start and
to get fast, and may use more memory. The JVM configuration is requested using
--jvm. To check you are using the JVM configuration,
ruby --version should
If you are running a short-running program you probably want the default,
native, configuration. If you are running a long-running program and want the
highest possible performance you probably want the JVM configuration, by using
At runtime you can tell if you are using the native configuration using
You won't encounter it when using TruffleRuby from the GraalVM, but there is
also another configuration which is TruffleRuby running on the JVM but with the
GraalVM Compiler not available. This configuration will have much lower
performance and should normally only be used for development.
Interpreter for this configuration.
TruffleRuby is actively tested on these systems:
- Oracle Linux 7
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Fedora 28
- macOS 10.14 (Mojave)
- macOS 10.13 (High Sierra)
You may find that TruffleRuby will not work if you severely restrict the
environment, for example by unmounting system filesystems such as
- make for building C and C++ extensions.
- libssl for the
- zlib for the
Without these dependencies, many libraries including RubyGems will not work. TruffleRuby will try to print a nice error message if a dependency is missing, but this can only be done on a best effort basis.
You may also need to set up a UTF-8 locale.
We recommend that people trying TruffleRuby on their gems and applications get in touch with us for help.
TruffleRuby is progressing fast but is currently probably not ready for you to try running your full Rails application on. However it is ready for experimentation and curious end-users to try on their gems and smaller applications, and to send us reports of issues they find.
Migration from MRI
TruffleRuby should in most cases work as a drop-in replacement for MRI, but you should read about our compatibility.
Migration from JRuby
For many use cases TruffleRuby should work as a drop-in replacement for JRuby. However, our approach to integration with Java is different to JRuby so you should read our migration guide.
Extensive documentation is available in
Please report security vulnerabilities via the process outlined at reporting vulnerabilities guide, rather than by something public such as a GitHub issue or a Gitter conversation.
Announcements about GraalVM, including TruffleRuby, are made on the graal-dev mailing list.
The main authors of TruffleRuby ordered by first contribution are:
- Chris Seaton
- Benoit Daloze
- Kevin Menard
- Petr Chalupa
- Brandon Fish
- Duncan MacGregor
- Christian Wirth
- Rafael França
- Alan Wu
- Thomas Würthinger
- Matthias Grimmer
- Josef Haider
- Fabio Niephaus
- Matthias Springer
- Lucas Allan Amorim
- Aditya Bhardwaj
See the security documentation.
TruffleRuby is copyright (c) 2013-2019 Oracle and/or its affiliates, and is made available to you under the terms of any one of the following three licenses:
- Eclipse Public License version 2.0, or
- GNU General Public License version 2, or
- GNU Lesser General Public License version 2.1.