Heroku 2014: A Year in Review
summary
Heroku reports concrete wins: deployment times drop about 40% faster deploys by using parallel installs (Bundler 1.5 -j), PIGz compression, asset caching (Rails 4 reduces median deploys from ~32s to ~14s) and fewer duplicate downloads. Platform adds PX dynos (6GB, 8 cores), HTTP Request ID and Log Runtime Metrics for tracing. Runtime advice favors Puma hybrid threads/processes to increase in-dyno concurrency and reduce queueing. Ruby support moves to 2.0+, ongoing GC and perf work (RGenGC, bug fixes) improves stability.
AI-written summary · about
chapters (21)
- 0:00Start
- 0:17Heroku 2014: A Year in Review
- 1:12Community Features
- 2:563 Ways to make code faster
- 5:18Parallel Gzip
- 14:57How do we get more consistent performance?
- 15:29Scaling: With Dynos Inside
- 17:02Puma (unlike Unicorn) can run multiple threads in each process (hybrid mode)
- 24:09forks becomes cheaper
- 24:49Platform Visibility
- 25:35Log Runtime Metrics
- 27:54Declare your ruby version in your Gemfile
- 30:13Matz Ruby Team Update
- 32:13The Patch Monster
- 36:08Faster code execution, shorter GC pauses
- 39:03Working on infrastructure services to help with testing Ruby
- 39:26WANTED: Ruby 2.2 Feature Ideas
- 39:48PSA: please set your Ruby version in your Gemfile
- 40:06Who has heard of secrets.yml?
- 43:10Concurrency and Database Connections in Ruby with
- 43:48The Asset pipeline: railsconf The number one source of Heroku
