In Rails, sometimes we need to iterate over all the records from a model.
To achieve this people prefer to use
all.each on a model.
This can lead to usage of memory if there are millions (huge number of) records in the table.
Let’s say we have a model
We will compare the usage of
to see which the differences
when to use
When we perform all.each on a model in Rails, it loads all the records from the table in memory and then iterates over those records.
When we call
it will query the database
to fetch all the user records
The query fired
when we execute
is shown below.
This can lead to
a lot of memory being used
as there is no
offset is used
when querying database.
The find_each approach internally uses batches to query and get records in memory.
Here is the Rails source code for the find_each method.
find_each method accepts an hash with following options.
batch_size: Specifies the size of the batch.
batch_sizeis defaulted to 1000
start: This is a value of primary key to start records from for the query. Inclusive of the value.
finish: This is a value of primary key to finish records from for the query. Inclusive of the value.
error_on_ignore: Overrides the application config to specify if an error should be raised when an order is present in the relation.
We can see that
find_each internally makes use
which queries database in batches.
Even though we do not pass parameters
it makes sure that query is done
of size 1000 (default
Thus, even though we feel that the table has less number of records,
we can make use of
find_each as a good practice.
find_each will take care of using
if number of records are greater than
It also gives additional benefit of not hogging up
Feel free to comment on with your opinions.
Subscribe to Ruby in Rails
Get the latest posts delivered right to your inbox