Skip to content
Branch: master
Find file Copy path
Find file Copy path
3 contributors

Users who have contributed to this file

@FooBarWidget @jamatthews @vlado
624 lines (381 sloc) 37 KB

Fullstaq Ruby Server Edition: a server-optimized Ruby distribution

Fullstaq Ruby is a Ruby distribution that's optimized for use in servers. It is the easiest way to:

  • Install Ruby on servers — we supply precompiled binaries.
  • Keep Ruby security-patched or up-to-date — integrates with your OS package manager.
  • Significantly reduce memory usage of your Ruby apps — a memory reduction of 50% is quite realistic.
  • Increase performance — thanks to the usage of better memory allocators.

You can think of Fullstaq Ruby as a competitor of apt/yum install ruby, rbenv install and rvm install. We supply native OS packages for various Ruby versions, which are optionally compiled with Jemalloc or malloc_trim, allowing for lower memory usage and potentially increased performance. Our packaging method allows much easier security patching.

Fullstaq Ruby is a work-in-progress! Features like APT/YUM repo, editions optimized for containers and Heroku, and much more, are planned. Please see our roadmap.

Table of contents:

Key features

  • Precompiled binaries: save time and energy, increase security

    Stop wasting time and energy with compiling Ruby or applying source patches. We supply precompiled Ruby binaries so that you don't have to. Improve security by eliminating the need to install a compiler on your server.

  • Native OS packages: install and update with tools you already use

    We supply our binaries as native OS packages (e.g. via APT, YUM). Easily integrate with your configuration management tools, no need to integrate yet another installer. Easily keep Ruby security-patched or up-to-date with tools you already use.

  • Jemalloc and malloc_trim integration: reduce memory usage, increase performance

    Main articles:

    In Hongli Lai's research project What Causes Ruby Memory Bloat?, Hongli has identified the OS memory allocator as a major cause of memory bloating in Ruby.

    There are two good solutions for this problem: either by using the Jemalloc memory allocator, or by using the malloc_trim API.

    Both solutions require patching the Ruby interpreter, but we've done that for you so that you don't have to. Use our binaries, and benefit from reduced memory usage and potentially increased performance out-of-the-box and in a hassle-free manner.

  • Multiple Ruby versions: ensure compatibility

    Not all apps are deployed against the latest Ruby — at least, not all the time. We supply binaries for multiple Ruby versions. Enjoy the benefits of Fullstaq Ruby no matter which Ruby version you use.

  • Rbenv integration: manage Ruby versions with already-familiar tools

    Our multi-Ruby support works by integrating with the popular Ruby version manager Rbenv. Continue to benefit from Rbenv ecosystem tooling like capistrano-rbenv. No need to learn another tool for managing Ruby versions.


Why was Fullstaq Ruby created?

Fullstaq Ruby came about for two reasons:

  • Optimizing for server use cases.

    Ruby uses a lot of memory. In fact, way too much and much more than it is "supposed to". Fortunately, there are "simple" solutions that provide a lot of benefit to users without requiring difficult code changes in Ruby: by compiling Ruby against the Jemalloc memory allocator, or by modifying Ruby to make use the malloc_trim API. In case you use Jemalloc, you even get a nice performance improvement.

    Main articles:

    Unfortunately for people who use Ruby in server use cases (e.g. most Ruby web apps), Ruby core developers are a bit careful/conservative and are hesitant to adopt Jemalloc, citing concerns that Jemalloc may cause regressions in non-server use cases, as well as other compatibility-related concerns.

    That's where Fullstaq Ruby comes in: we are opinionated. Fullstaq Ruby does not care about non-server use cases, and we prefer a more progressive approach, so we make choices to optimize for that use case.

  • Installing the Ruby version you want, and keeping it security-patched, is a miserable experience.

    The most viable ways to install Ruby are:

    1. From OS repositories, e.g. apt install ruby/yum install ruby.
    2. Compiling Ruby using a version manager like RVM or Rbenv.
    3. Installing precompiled binaries supplied by RVM or Rbenv.

    All of these approaches have problems:

    • OS repos drawbacks:

      • They don't always have the Ruby minor version that you want (or they require you to upgrade your distro to get the version you want).
      • There is no way to install a specific tiny version.
      • Very bad support for managing multiple Ruby versions (e.g. can't easily activate a different Ruby on a per-user or per-project basis).
    • Compilation via RVM/Rbenv drawbacks:

      • Requires a compiler, which is a security risk.
    • RVM/Rbenv (whether compilation or precompiled binaries) drawbacks:

      • Keeping Ruby security-patched is a hassle.
      • Upgrading to a new Ruby tiny version (e.g. 2.5.0 -> 2.5.1) requires explicit intervention.
      • After upgrading the Ruby tiny version, you need to update all your application servers and deployment code to explicitly use that new version, and you need to reinstall all your gems.

    Fullstaq Ruby addresses all of these problems by combining native OS packages and Rbenv. See How it works

Who is behind Fullstaq Ruby?

  • Fullstaq Ruby is created by Hongli Lai, CTO at Phusion, author of the Passenger application server, and creator of the now-obsolete Ruby Enterprise Edition.
  • Fullstaq Ruby is created in partnership with Fullstaq, a cloud native, Kubernetes and DevOps technology partner company in the Netherlands.

If you like this work, please star this repo, follow @honglilai on Twitter, and/or contact Fullstaq. Fullstaq can take your technology stack to the next level by providing consultancy, training, and much more.

How it works

See also: Installation

The Fullstaq Ruby native OS packages allow you to install Rubies by adding our repository and installing them through the OS package manager. The highlights are:

  • Native OS packages.

    Rubies are installed by adding our repository and installing through the OS package manager.

  • We supply packages for each minor version.

    For example, there are packages for Ruby 2.5 and 2.6. These packages always contain the most recent tiny version. Learn more below in subsection Minor version packages.

  • We also supply packages for each tiny version.

    If you require a very specific tiny version: we support that too! For example we have packages for 2.5.5 and 2.6.0.

  • 3 variants for each Ruby version: normal, jemalloc, malloctrim.

    Learn more below in subsection About variants.

  • Each Ruby installation is just a normal directory.

    When you install a Ruby package, files are placed in /usr/lib/fullstaq-ruby/versions/<VERSION>.

  • We supply Rbenv as a native OS package.

    We use Rbenv to switch between different Ruby versions. Rbenv has been slightly modified to support the notion of system-wide Ruby installations.

  • All Ruby packages register a Ruby version inside the Rbenv system.

    This registration is done on a system-wide basis (in /usr/lib/rbenv/versions, as opposed to ~/.rbenv/versions).

  • Parallel packages.

    All Ruby versions — and all their variants — are installable in parallel.

Package organization

See also: Installation

Let's say you're on Ubuntu (RHEL/CentOS packages use a different naming scheme). Let's pretend Fullstaq Ruby only packages Ruby 2.6.2 and Ruby 2.6.3 (and let's pretend the latter is also the latest release). You will be able to install the following packages:

  • Version 2.6:
    • Normal variant: fullstaq-ruby-2.6
    • Jemalloc variant: fullstaq-ruby-2.6-jemalloc
    • Malloctrim variant: fullstaq-ruby-2.6-malloctrim
  • Version 2.6.2:
    • Normal variant: fullstaq-ruby-2.6.2
    • Jemalloc variant: fullstaq-ruby-2.6.2-jemalloc
    • Malloctrim variant: fullstaq-ruby-2.6.2-malloctrim
  • Version 2.6.3:
    • Normal variant: fullstaq-ruby-2.6.3
    • Jemalloc variant: fullstaq-ruby-2.6.3-jemalloc
    • Malloctrim variant: fullstaq-ruby-2.6.3-malloctrim

All these packages can be installed in parallel. None of them conflict with each other, not even the variants.

Rbenv integration

Suppose you install all packages listed in the Package organization example. That will register Rubies in the system-wide Rbenv versions directory:

  • /usr/lib/rbenv/versions/2.6
  • /usr/lib/rbenv/versions/2.6-jemalloc
  • /usr/lib/rbenv/versions/2.6-malloctrim
  • /usr/lib/rbenv/versions/2.6.2
  • /usr/lib/rbenv/versions/2.6.2-jemalloc
  • /usr/lib/rbenv/versions/2.6.2-malloctrim
  • /usr/lib/rbenv/versions/2.6.3
  • /usr/lib/rbenv/versions/2.6.3-jemalloc
  • /usr/lib/rbenv/versions/2.6.3-malloctrim

These registrations are symlinks. The actual Ruby installation is in /usr/lib/fullstaq-ruby. So for example, one symlink looks like this:

/usr/lib/rbenv/versions/2.6 -> /usr/lib/fullstaq-ruby/versions/2.6

If you run rbenv versions, you'll see:

$ rbenv versions
* system (set by /home/hongli/.rbenv/version)

Installed Fullstaq Rubies are available to all users on the system. They complement any Rubies that may be installed in ~/.rbenv/versions.

You activate a specific version by using regular Rbenv commands:

 $ rbenv local 2.6.3
 $ rbenv exec ruby -v
 ruby 2.6.3

 $ rbenv local 2.6.3-jemalloc
 $ rbenv exec ruby -v
 ruby 2.6.3 (jemalloc variant)

Minor version packages: a great way to keep Ruby security-patched

fullstaq-ruby-2.6.2 and fullstaq-ruby-2.6.3 are tiny version packages. They package a specific tiny version.

fullstaq-ruby-2.6 is a minor version package. It always contains the latest tiny version! If today the latest Ruby 2.6 version is 2.6.3, then fullstaq-ruby-2.6 contains 2.6.3. If tomorrow 2.6.4 is released, then fullstaq-ruby-2.6 will be updated to contain 2.6.4 instead.

We recommend installing the minor version package/image over installing tiny version packages/images:

  • No need to regularly check whether the Ruby developers have released a new tiny versions. The latest tiny version will be automatically installed as part of the regular OS package manager update process (e.g. apt upgrade/yum update). This is safe because Ruby follows semantic versioning.

  • No need to reinstall all your gems or update any configuration files after a tiny version update has been installed. A minor version package utilizes the same paths, regardless of the tiny version that it contains.

    For example, the fullstaq-ruby-2.6 package always contains the following, no matter which tiny version it actually is:

    • /usr/lib/rbenv/versions/2.6/bin/ruby
    • /usr/lib/rbenv/versions/2.6/lib/ruby/gems/2.6.0

About variants

So there are 3 variants: normal, jemalloc, malloctrim. What are the differences?

  • Normal: The original Ruby. No third-party patches applied.

    Normal variant packages have no suffix, e.g.: apt install fullstaq-ruby-2.6.2

  • Jemalloc: Ruby is linked to the Jemalloc memory allocator.

    • Pro: Uses less memory than the original Ruby.
    • Pro: Is usually faster than the original Ruby. (How much faster? AppFolio benchmark, Ruby Inside benchmark)
    • Con: May not be compatible with all gems (though such problems should be rare).

    Learn more: What is Jemalloc and how does it benefit me?

    Jemalloc variant packages/images have the -jemalloc suffix, e.g.: apt install fullstaq-ruby-2.6.2-jemalloc

  • Malloctrim: Ruby is patched to make use of the malloc_trim API to reduce memory usage.

    • Pro: Uses less memory than the original Ruby.
    • Pro: Unlike jemalloc, there are no compatibility problems.
    • Con: May be slightly slower. (How much slower?)

    Learn more: What is malloc_trim and how does it benefit me?

    Malloctrim variant packages/images have the -malloctrim suffix, e.g.: apt install fullstaq-ruby-2.6.2-malloctrim

Recommendation: use the jemalloc variant, unless you actually observe compatibility problems.

Comparisons to other systems

Vs RVM and Rbenv

RVM and Rbenv are Ruby version managers. They allow you to install and switch between multiple Ruby versions. They allow installing Ruby by compiling from source, or sometimes by downloading precompiled binaries (the availability of binaries for different platforms is limited).

Fullstaq Ruby is not a Ruby version manager. Fullstaq Ruby is a Ruby distribution: we supply binaries for Ruby. You can think of Fullstaq Ruby as a replacement for rvm install and rbenv install.

The differences between rvm/rbenv install and Fullstaq Ruby are:

  • Fullstaq Ruby is installed via the OS package manager. Rubies installed with rvm/rbenv install are not managed via the OS package managers.

  • Fullstaq Ruby updates are supplied through the OS package manager, which can be easily automated. Updates using rvm/rbenv install require more effort.

  • When you upgrade Ruby using rvm/rbenv install, the path to Ruby and the gem path changes, and so you will need to reinstall all gems and explicit reconfigure application servers to use the upgraded Ruby version -- even if you upgrade to a newer tiny version.

    Fullstaq Ruby supports the concept of minor version packages, which solves this hassle, making security patching much easier.

  • Fullstaq Ruby provides Ruby variants with Jemalloc and malloc_trim integration. RVM and Rbenv do not.

    The Jemalloc and malloc_trim variants allow significant reduction in memory usage, and possibly also performance improvements. Learn more: What is Jemalloc and how does it benefit me?, What is malloc_trim and how does it benefit me?

    RVM and Rbenv still allow you to apply the Jemalloc and malloc_trim patches, but they don't provide binaries for that (while Fullstaq Ruby does) and so you will be required to compile from source.

Vs Ruby packages included in operating systems' official repositories

  • Many operating systems' official repositories only provide a limited number of Ruby versions. If the Ruby version you want isn't available, then you're out of luck: you'll need to upgrade or downgrade the entire OS to get that version, or you need to install it using some other method.

    Fullstaq Ruby provides native OS packages for many more Ruby versions, for multiple OS versions.

  • The Ruby packages provided by many OS repositories also don't allow you to easily switch between versions on a per-user or per-app basis.

    Fullstaq Ruby allows easy switching between versions by integrating with Rbenv.

  • OS repositories package specific minor versions of Ruby. They regularly update their packages to the latest tiny version for that minor package. This is good for security-patching reasons, but if you need to install a specific tiny Ruby version (e.g. for compatibility reasons) then you're out of luck.

    Fullstaq Ruby provides both minor version packages and specific tiny version packages.

  • Fullstaq Ruby provides Jemalloc and malloc_trim integration. OS official repositories do not.

    The Jemalloc and malloc_trim variants allow significant reduction in memory usage, and possibly also performance improvements. Learn more: What is Jemalloc and how does it benefit me?, What is malloc_trim and how does it benefit me?

Vs the Brightbox PPA

The Brightbox PPA is an Ubuntu APT repository provided by Brightbox.

Like Fullstaq Ruby, the Brightbox PPA contains packages for multiple Ruby versions, for multiple Ubuntu versions.

The differences are:

Vs JRuby, TruffleRuby and Rubinius

JRuby, TruffleRuby and Rubinius are alternative Ruby implementations, that are different from the official Ruby (MRI).

Fullstaq Ruby is not an alternative Ruby implementation. It is a distribution of MRI.

Vs LD_PRELOADing Jemalloc yourself

You can enjoy reduced memory usage and higher performance with a do-it-yourself solution that involves LD_PRELOADing Jemalloc. The difference with Fullstaq Ruby is not on a technical level, but on a service level.

With a DIY solution, you are responsible for lifecycle management and for ensuring that the right version of Jemalloc is picked. Only Jemalloc 3 yields reduced memory usage, Jemalloc 5 does not. If you for example install Jemalloc from your distribution's package manager, then you must double-check that your distribution doesn't distribute a too new Jemalloc.

You can of course install Jemalloc from source (assuming you don't mind compiling). But then you become responsible for keeping it security-patched.

Fullstaq Ruby, ensures that the right version of Jemalloc is used. We are a bunch of people that care about this subject, so we are constantly researching better ways to integrate Jemalloc. For example there are some efforts on the way to research how to make use of Jemalloc 5. We also keep an eye on security issues and supply security updates, so that you can sit back and relax.



  • Supported RHEL/CentOS versions: 7
  • Supported architectures: x86-64

We don't have a YUM repository yet. That is planned for epic 2 in the roadmap.

You can find RPMs in the Github releases page. Please download two files:

  1. The fullstaq-rbenv RPM.
  2. A Ruby RPM that matches the Ruby version, variant and distribution you want, e.g. fullstaq-ruby-2.6-jemalloc-rev0-centos-7.x86_64.rpm.

We recommend that you download a minor version package, e.g. 2.6 instead of 2.6.3. That way you can easily stay up-to-date with tiny version upgrades and security patches.

After downloading, install them both with YUM:

sudo yum install fullstaq-rbenv-[...].noarch.rpm fullstaq-ruby-[...]-centos-7.x86_64.rpm

Note that you can even install multiple versions in parallel if you really want to. E.g. you can install a 2.6, 2.6.3 and 2.5.5 in parallel.

Next steps:


  • Supported Debian versions: 9
  • Supported Ubuntu versions: 18.04
  • Supported architectures: x86-64

We don't have an APT repository yet. That is planned for epic 2 in the roadmap.

You can find DEBs in the Github releases page. Please download two files:

  1. The fullstaq-rbenv DEB.
  2. A Ruby DEB that matches the Ruby version, variant and distribution you want, e.g. fullstaq-ruby_2.6-jemalloc_0-ubuntu-18.04_amd64.deb.

We recommend that you download a minor version package, e.g. 2.6 instead of 2.6.3. That way you can easily stay up-to-date with tiny version upgrades and security patches.

After downloading, install them both with APT:

sudo apt install ./fullstaq-rbenv_[...]_all.deb ./fullstaq-ruby_[...]_amd64.deb

Note: be sure to pass a directory prefix like ./ to apt install, otherwise APT won't recognize them as files and will think they're package names in APT!

Also note that you can even install multiple versions in parallel if you really want to. E.g. you can install a 2.6, 2.6.3 and 2.5.5 in parallel.

Next steps:

Deactivate Git-based Rbenv

Note: you only need to perform this step if you already had a Git-based Rbenv installed. Otherwise you can skip to the next step: Activate Rbenv shell integration.

Fullstaq-Ruby relies on a sightly modified version of Rbenv, for which we supply an OS package. This package installs the rbenv binary to /usr/bin.

You should modify your shell files to remove your Git-based Rbenv installation from your PATH, so that /usr/bin/rbenv is used instead. For example in your .bash_profile and/or .bashrc, remove lines that look like this:

# REMOVE lines like this!
export PATH="$HOME/.rbenv/bin:$PATH"

There is no need to remove eval "$(rbenv init -)". You're still going to use Rbenv — just one that Fullstaq Ruby provides. More about that in the next step, Activate Rbenv shell integration.

There is also no need to remove the ~/.rbenv directory. The Ruby versions installed in there are still supported — in addition to system-wide ones installed by the Fullstaq Ruby packages.

Activate Rbenv shell integration (optional)

Note: you only need to perform this step if you didn't already have Rbenv shell integration installed. You can skip this step if you already had Rbenv shell integration installed from a previous Git-based Rbenv installation.

For an optimal Rbenv experience, you should activate its shell integration.

Run this command, which will tell you to add some code to one of your shell files (like .bashrc or .bash_profile):

/usr/bin/rbenv init

Be sure to restart your shell after installing shell integration.

System-wide shell integration

Adding to .bashrc/.bash_profile only activates the shell integration for that specific user. If you want to activate shell integration for all users, you should add to a system-wide shell file. For example if you're using bash, then:

  • Ubuntu: /etc/bash.bashrc
  • RHEL/CentOS: /etc/bashrc

Usage after installation

Using a specific Ruby version

Ruby versions are installed to /usr/lib/fullstaq-ruby/versions/<VERSION>. Each such directory has a bin subdirectory which contains ruby, irb, gem, etc.

Suppose you installed Ruby 2.6 (normal variant). You can execute it directly:

$ /usr/lib/fullstaq-ruby/versions/2.6/bin/ruby --version
ruby 2.6.3

$ /usr/lib/fullstaq-ruby/versions/2.6/bin/gem install --no-document nokogiri

But for convenience, it's better to add /usr/lib/fullstaq-ruby/versions/<VERSION>/bin to your PATH so that you don't have to specify the full path every time. See Activate Rbenv shell integration (optional).

Usage with Rbenv

The recommended way to use Fullstaq Ruby is through the Rbenv integration. You should learn Rbenv if you are not familiar with it. Here is a handy cheat sheet.

Suppose you installed Ruby 2.6 (normal variant). You can run that Ruby by setting RBENV_VERSION and prefixing yours commands with rbenv exec:

$ export RBENV_VERSION=2.6
$ rbenv exec ruby --version
ruby 2.6.3
$ rbenv exec gem env

Or, if you've activated the Rbenv shell integration, just running ruby, gem and various other Ruby would also work, provided that you've activated a certain version and that there's an Rbenv shim available:

$ rbenv local 2.6
$ ruby --version
ruby 2.6.3
$ gem env

Passenger for Nginx/Apache integration

First, find out the full path to the Ruby version's binary that you want to use: Using a specific Ruby version.

Next, specify it in the Nginx or Apache config file:

  • Nginx: passenger_ruby <full path to ruby executable>;
  • Apache: PassengerRuby <full path to ruby executable>

Restart Nginx or Apache after you've made the change.

Puma, Unicorn or Passenger Standalone integration

First, find out the full path to the Ruby version's binary that you want to use: Using a specific Ruby version.

Next, modify your Puma/Unicorn/Passenger Standalone startup script (e.g. Systemd unit) and make sure that it executes your application server using the full path to your Ruby executable. This is usually done by modifying the ExecStart option.

For example suppose you have a Systemd unit file /etc/systemd/system/puma.service that looks like this:

# Just an example!

Description=Puma HTTP Server

ExecStart=/home/app/.rbenv/versions/2.5.5/bin/ruby -S bundle exec puma -C puma.rb


Make sure that your ExecStart command is prefixed by a call to /full-path-to-ruby -S, like this:

ExecStart=/usr/lib/fullstaq-ruby/versions/2.6.3-jemalloc/bin/ruby -S bundle exec puma -C puma.rb

Don't forget the -S!

Restart your application server after you've made a change, for example sudo systemctl restart puma.

Capistrano integration

If you use Capistrano to deploy your app, then you should use the capistrano-rbenv plugin. In your deploy/config.rb make sure you set rbenv_ruby to the Ruby version to you want, possibly with a variant suffix. Examples:

# Use Ruby 2.6 (latest tiny version), normal variant
set :rbenv_ruby, '2.6'

# Use Ruby 2.6.3, normal variant
set :rbenv_ruby, '2.6.3'

# Use Ruby 2.6.3, jemalloc variant
set :rbenv_ruby, '2.6.3-jemalloc'


What is Jemalloc and how does it benefit me?

Jemalloc is the FreeBSD libc memory allocator. It uses a more complex algorithm than the default Linux glibc memory allocator, but is faster and results in less memory fragmentation (which reduces memory usage significantly). Jemalloc has been used successfully by e.g. Firefox and Redis to reduce their memory footprint and ongoing development is supported by Facebook.

What is malloc_trim and how does it benefit me?

malloc_trim() is an API that is part of the glibc memory allocator. In Hongli Lai's research project What Causes Ruby Memory Bloat?, Hongli has identified the OS memory allocator as a major cause of memory bloating in Ruby. Luckily, simple fixes exist, and one fix is to invoke malloc_trim() which tells the glibc memory allocator to release free memory back to the kernel.

It is found that, if Ruby calls malloc_trim() during a garbage collection, then memory usage can be reduced significantly.

However, malloc_trim may have some performance impact.

Is Fullstaq Ruby faster than regular Ruby (MRI)?

If you pick the Jemalloc variant, then yes it is often faster. See About variants. See also these benchmarks:

Why does Fullstaq Ruby integrate with Rbenv?

Many users have a need to install and switch between multiple Rubies on a single machine, so we needed a Ruby version manager. Rather than inventing our own, we chose to use Rbenv because it's popular and because it's easy to integrate with.

I do not need multiple Rubies (and have no need for Rbenv), is Fullstaq Ruby suitable for me?

Yes. The multi-Ruby-support via Rbenv is quite lightweight and is unintrusive, weighting a couple hundred KB at most. Even if you do not need Rbenv, the fact that Fullstaq Ruby uses Rbenv doesn't get in your way and does not meaningfully increase resource utilization.

Which variant should I pick?

See: About variants.

Why a new distribution? Why not contribute to Ruby core?

The Ruby core team is reluctant or slow to incorporate certain changes. And for a good reason: whether a change is an improvement depends on the perspective. The Ruby core team has to care about a wide range of users and use cases. Incorporating Jemalloc or malloc_trim is not necessarily an improvement for all their users.

While understandable, that attitude does not help users for which those changes are actual improvement. Fullstaq Ruby's goal is to help people who use Ruby in a server context, in production environments, on x86-64 Linux. For example we don't care about development environments like macOS, or Raspberry PIs. This allows us to make less conservative choices than the Ruby core team.

Furthermore, the Ruby core team does not want to be responsible for certain aspects, such as distributing binaries. But binaries are valuable. So we take up the responsibility of packaging binaries.

The Ruby core team have debated for years on whether to incorporate Jemalloc, and so far they've only been reluctant. Furthermore, Hongli Lai's research and discussions with various experts have revealed that the only way to make optimal use of Jemalloc is through the LD_PRELOAD mechanism: compiling Ruby with --with-jemalloc is not enough! LD_PRELOAD is such an intrusive and platform-specific change, that we're confident that the Ruby core team will never accept using such a mechanism by default.

In short: Fullstaq Ruby's goal is to bring value to server-production users as soon as possible, and we think maintaining our own distribution is the fastest and best way to achieve that goal.

Will Fullstaq Ruby become paid in the future?

There will be no paid version. Fullstaq Ruby is fully open source. It is also intended to be a community project where anyone can contribute. There are no monetization plans.

I am wary of vendor lock-in or that I will become dependent on a specific party for supplying packages. What is Fullstaq Ruby's take on this?

Vendor lock-in is a valid concern that many of us have. It is something we thought about from the beginning and that are are addressing.

We have architected our systems in such a way that anyone will be able to build packages themselves. If we ever become slow or defunct, then anyone can easily take matters into own hands. Building Fullstaq Ruby packages from your own systems is so simple that nearly anyone can do it: just install Docker, edit a config file and run a command.

This is achieved by automating the entire build process, and by releasing the making the build tooling as open source. There are almost no manual processes. Please take a look at this repository's source code.

Because Fullstaq Ruby is still a work-in-progress, we don't have documentation yet on how to build packages yourself. Such documentation is planned for epic 5 of the roadmap.

You can’t perform that action at this time.