Rodrigo Rosenfeld Rosas
In my previous article we explored how we can build huge web app monoliths with Ruby that can complete simple request tests in under a second. In this article we’ll focus on Rails apps. We’ll identify what causes a big app to take a long time to boot and run simple tests and what we can do to improve the situation.
Let’s start by investigating how fast we can expect a Rails app to boot. Let’s check against a minimal Rails app first:
We can’t get subsecond testing with Rails using hardware commonly used in a development environment, like we did with Rack and Roda in my previous article, but we can get pretty close with a minimal Rails app. How about a full Rails app?
Not that bad. This is what we can expect from a fresh full Rails app. If we can keep our tests running that fast, that should be good enough.
If you’re reading this article, chances are that you are from the days where Spring was added by default when you ran “rails new app”. You might be asking: what about Spring?
.png?sfvrsn=fed1995f_5)
