Rubocop VS Scientist

No, it's not?! The latest version is 1.28.2: https://rubygems.org/gems/rubocop

Running rubocop might give you a few tips regarding naming conventions and best practices

Check out GitHub scientist if you are doing a migration with a ruby based system: https://github.com/github/scientist

Great support and functionality for testing differences between two systems of record.

However, the good news is that it’s easy and safe to do so in Ruby and Rails using the Scientist gem. Scientist's name is based on the scientific method of conducting experiments to verify a given hypothesis. In this case, our hypothesis is that the new code does the job.

Github scientist.

You could try using both gems and wrapping a few instances (or all) of your pagination logic in the scientist gem. I can't recall offhand if it has benchmarking built-in, but you could easily wrap your use and try blocks in benchmarking calls and compare that when you publish results.

But there's an even better option: run both libraries in production for real-world requests, and see if there's a meaningful gain from undici. I learnt this approach from GitHub's Scientist. Sadly, this article is about tracing, not experimentation, so I won't continue down that path now, but I hope to write another article about it soon. My implementation would probably be to have a switch that randomly picks one of the two libraries for each request. Then I'll compare the metrics and see which performs better over time.