RoRvsWild
@rorvswild.com
All-in-one monitoring for Ruby on Rails applications.
Track performances and errors for requests and background jobs.
https://www.rorvswild.com
Track performances and errors for requests and background jobs.
https://www.rorvswild.com
🤔 Exceptions in Markdown (add .md to URLs). What would you do with this?
October 29, 2025 at 9:12 AM
🤔 Exceptions in Markdown (add .md to URLs). What would you do with this?
We don't need catch, throw and redo either, because unrolling loops is faster!
October 8, 2025 at 7:24 AM
We don't need catch, throw and redo either, because unrolling loops is faster!
This method has been entirely generated by AI. If you care about performances, you still have a job :-)
June 19, 2025 at 4:01 PM
This method has been entirely generated by AI. If you care about performances, you still have a job :-)
Read The Nice Manual!
In the happy world of #Ruby, we don’t #RTFM, we #RTNM
New documentation website for Ruby, Rails, and a bunch of selected gems:
rubyrubyrubyruby.dev
Short intro post:
www.rorvswild.com/blog/2025/re...
Contribute:
github.com/BaseSecrete/...
Wdyt?
In the happy world of #Ruby, we don’t #RTFM, we #RTNM
New documentation website for Ruby, Rails, and a bunch of selected gems:
rubyrubyrubyruby.dev
Short intro post:
www.rorvswild.com/blog/2025/re...
Contribute:
github.com/BaseSecrete/...
Wdyt?
June 4, 2025 at 9:37 AM
Read The Nice Manual!
In the happy world of #Ruby, we don’t #RTFM, we #RTNM
New documentation website for Ruby, Rails, and a bunch of selected gems:
rubyrubyrubyruby.dev
Short intro post:
www.rorvswild.com/blog/2025/re...
Contribute:
github.com/BaseSecrete/...
Wdyt?
In the happy world of #Ruby, we don’t #RTFM, we #RTNM
New documentation website for Ruby, Rails, and a bunch of selected gems:
rubyrubyrubyruby.dev
Short intro post:
www.rorvswild.com/blog/2025/re...
Contribute:
github.com/BaseSecrete/...
Wdyt?
Where's Waldo #HelveticRuby Geneva Edition™
May 28, 2025 at 6:08 PM
Where's Waldo #HelveticRuby Geneva Edition™
Here's my recipe to increase code coverage:
1. Set minimum code coverage with current value 📏
2. You're not allowed to decrease it ⛔️
3. Every week check the value and increase the minimum accordingly 🔄
4. Code coverage will slowly but magically increase ⬆️
1. Set minimum code coverage with current value 📏
2. You're not allowed to decrease it ⛔️
3. Every week check the value and increase the minimum accordingly 🔄
4. Code coverage will slowly but magically increase ⬆️
May 1, 2025 at 8:54 AM
Here's my recipe to increase code coverage:
1. Set minimum code coverage with current value 📏
2. You're not allowed to decrease it ⛔️
3. Every week check the value and increase the minimum accordingly 🔄
4. Code coverage will slowly but magically increase ⬆️
1. Set minimum code coverage with current value 📏
2. You're not allowed to decrease it ⛔️
3. Every week check the value and increase the minimum accordingly 🔄
4. Code coverage will slowly but magically increase ⬆️
Maybe this, to avoid locking in the happy path.
March 18, 2025 at 8:34 AM
Maybe this, to avoid locking in the happy path.
One more good reason to come at Geneva.rb on the 12 march: after the talk we will eat a fondue 🫕 at Bains des Pâquis. Even if you far, or abroad, it worth it 😋
March 7, 2025 at 8:20 AM
One more good reason to come at Geneva.rb on the 12 march: after the talk we will eat a fondue 🫕 at Bains des Pâquis. Even if you far, or abroad, it worth it 😋
Avoid returning records from a model's method
Because a SQL query is triggered on each call. Memoizing the result is not necessarily better since it won't be uncached when reload is called. Instead, switch that method to a relation.
Because a SQL query is triggered on each call. Memoizing the result is not necessarily better since it won't be uncached when reload is called. Instead, switch that method to a relation.
November 29, 2024 at 9:56 AM
Avoid returning records from a model's method
Because a SQL query is triggered on each call. Memoizing the result is not necessarily better since it won't be uncached when reload is called. Instead, switch that method to a relation.
Because a SQL query is triggered on each call. Memoizing the result is not necessarily better since it won't be uncached when reload is called. Instead, switch that method to a relation.
One step further
It works fine with a few thousand. But that would probably eat too much memory if you're loading a lot of ActiveRecord instances. The trick is to load IDs only if you do not need to access any attributes or methods.
It works fine with a few thousand. But that would probably eat too much memory if you're loading a lot of ActiveRecord instances. The trick is to load IDs only if you do not need to access any attributes or methods.
November 25, 2024 at 3:57 PM
One step further
It works fine with a few thousand. But that would probably eat too much memory if you're loading a lot of ActiveRecord instances. The trick is to load IDs only if you do not need to access any attributes or methods.
It works fine with a few thousand. But that would probably eat too much memory if you're loading a lot of ActiveRecord instances. The trick is to load IDs only if you do not need to access any attributes or methods.
Enqueuing a lot a jobs really fast
Enqueuing via ActiveJob::Base#perform_later triggers callbacks and generates one round-trip for each job. Bulk enqueuing skips callbacks and enqueues all jobs in one step.
Enqueuing via ActiveJob::Base#perform_later triggers callbacks and generates one round-trip for each job. Bulk enqueuing skips callbacks and enqueues all jobs in one step.
November 25, 2024 at 3:57 PM
Enqueuing a lot a jobs really fast
Enqueuing via ActiveJob::Base#perform_later triggers callbacks and generates one round-trip for each job. Bulk enqueuing skips callbacks and enqueues all jobs in one step.
Enqueuing via ActiveJob::Base#perform_later triggers callbacks and generates one round-trip for each job. Bulk enqueuing skips callbacks and enqueues all jobs in one step.
Stop waiting for Redis responses with pipelining
Pipelining sends a bunch of commands without waiting for each individually. Instead of having N round-trips, there is only one, thus code is less idle. Of course, that's not possible when you need the result of the previous command for the next one.
Pipelining sends a bunch of commands without waiting for each individually. Instead of having N round-trips, there is only one, thus code is less idle. Of course, that's not possible when you need the result of the previous command for the next one.
November 15, 2024 at 9:49 AM
Stop waiting for Redis responses with pipelining
Pipelining sends a bunch of commands without waiting for each individually. Instead of having N round-trips, there is only one, thus code is less idle. Of course, that's not possible when you need the result of the previous command for the next one.
Pipelining sends a bunch of commands without waiting for each individually. Instead of having N round-trips, there is only one, thus code is less idle. Of course, that's not possible when you need the result of the previous command for the next one.
Importing a lot of records and their associations quickly
ActiveRecord's method insert_all is fast but limited when dealing with associations. Fortunately the gem activerecord-import has come to the rescue. It triggers a single query per table to avoid round-trips with the database.
ActiveRecord's method insert_all is fast but limited when dealing with associations. Fortunately the gem activerecord-import has come to the rescue. It triggers a single query per table to avoid round-trips with the database.
November 4, 2024 at 2:05 PM
Importing a lot of records and their associations quickly
ActiveRecord's method insert_all is fast but limited when dealing with associations. Fortunately the gem activerecord-import has come to the rescue. It triggers a single query per table to avoid round-trips with the database.
ActiveRecord's method insert_all is fast but limited when dealing with associations. Fortunately the gem activerecord-import has come to the rescue. It triggers a single query per table to avoid round-trips with the database.