Open Riak how we gained from leaning on the BEAM

on YouTube ↗40m

" summary

Migrated 20k lines of C++ to Erlang and redesigns give measurable wins: a 150M-object cluster on eight modest EC2 nodes (~$4k/month) stays stable at 100% CPU and tolerates a killed node with at most ~12.5% throughput loss while repairing 60M objects. Object size rises from 8KB to 80KB cut throughput only ~20%, and large-object throughput roughly doubles. Performance hunting uses eprof, eqwaliser, QuickCheck; most NIFs are removed (one zstd wrapper remains); fixes center on short‑lived processes, heap copying, and OTP upgrades. Release 3.4 RC targets spring, GA by Autumn 2025.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:02What Riak is
3. 3:51High availability goals
4. 11:15Riak’s evolution needs
5. 14:26Backend move to Erlang
6. 15:07Memory efficiency
7. 22:29CPU profiling
8. 28:06Performance outcomes
9. 32:20Riak’s future
10. 34:04Open Riak community
11. 36:43Q&A

" related talks

• 40mPerformance ImprovementsDavid Ansari · Code BEAM America 2022
• 19mErlang/OTP UpdateBjörn Gustavsson · Code BEAM Lite Stockholm 2026
• 39mUsing Erlang, Riak and the ORSWOT CRDT at bet365 (...)Michael Owen · Erlang User Conference 2015
• 48mGetting to Know the Erlang Virtual Machine, the BEAMNorberto Ortigoza · Mexico City Erlang Factory Lite 2015
• 52mOn the Scalability of the Erlang Virtual Machine and its Term StorageKostis Sagonas · Erlang Factory SF Bay Area 2014
• 43mThe RiverBruce Tate · Code Elixir LDN 2019
• 42mThe Soul of Erlang and ElixirSaša Jurić · GOTO Chicago 2019
• 46mEvents Analysis with Riak, Perl and Erlang at Booking.comDamien Krotkine · Code Mesh 2015