Seed data in Ruby on Rails - Performance & Optimization

Performance: Seed data

MEDIUM IMPACT

Seed data affects initial page load speed indirectly by impacting database size and query performance during development and testing.

Populating the database with initial data for development or testing

Ruby on Rails

users = (1..1000).map { |i| {name: "User #{i}", email: "user#{i}@example.com", created_at: Time.now, updated_at: Time.now} }
User.insert_all(users)

Inserts all users in a single bulk database operation, reducing query overhead.

📈 Performance GainSingle database insert operation, reducing seed time from seconds to milliseconds

Populating the database with initial data for development or testing

Ruby on Rails

1000.times do |i|
  User.create(name: "User #{i}", email: "user#{i}@example.com")
end

Creates records one by one, triggering a database insert for each user, causing many slow queries.

📉 Performance CostTriggers 1000 separate database insert operations, blocking seed script for seconds or more

Performance Comparison

Pattern	Database Operations	Query Count	Seed Time	Verdict
Single record inserts in loop	1000 inserts	1000 queries	Several seconds	[X] Bad
Bulk insert with insert_all	1 insert	1 query	Milliseconds	[OK] Good

Rendering Pipeline

Seed data does not directly affect browser rendering but impacts backend response times that influence initial page load speed.

→Database Query

→Server Response

⚠️ BottleneckDatabase insert and query time during seed and app startup

Core Web Vital Affected

LCP

Seed data affects initial page load speed indirectly by impacting database size and query performance during development and testing.

Optimization Tips

1Avoid inserting seed data one record at a time; use bulk inserts instead.

2Keep seed data minimal and relevant to reduce database size and query time.

3Seed data affects backend speed, which impacts initial page load and LCP.

Performance Quiz - 3 Questions

What is the main performance problem with creating seed data using a loop with individual create calls?

A It triggers many separate database insert queries, slowing down the seed process.

B It uses too much memory on the client side.

C It causes the browser to re-render multiple times.

D It increases CSS calculation time.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and observe backend response times for initial data requests.

What to look for: Look for long server response times indicating slow database queries caused by large seed data.

Practice

1. What is the main purpose of seed data in a Rails application?

easy

A. To run the Rails server

B. To create database tables automatically

C. To generate user interface templates

D. To fill the database with initial example data for testing and development

Solution

1. Step 1: Understand what seed data is

   Seed data is used to add example or default data into the database to help developers test and develop features easily.

2. Step 2: Identify the correct purpose

   Among the options, only filling the database with initial example data matches the purpose of seed data.

3. Final Answer:

   To fill the database with initial example data for testing and development -> Option D

4. Quick Check:

   Seed data purpose = Fill database with example data [OK]

Hint: Seed data = example info in database for testing [OK]

Common Mistakes:

• Confusing seed data with database schema creation
• Thinking seed data runs the server
• Assuming seed data generates UI templates

2. Which command correctly runs the seed file to load data into the database in Rails?

easy

A. rails generate seed

B. bin/rails db:seed

C. bin/rails db:create

D. rails server

Solution

1. Step 1: Recall the command to run seed data

   The standard command to load seed data in Rails is bin/rails db:seed.

2. Step 2: Check other options

   rails generate seed is not a valid command, bin/rails db:create creates the database, and rails server starts the server.

3. Final Answer:

   bin/rails db:seed -> Option B

4. Quick Check:

   Run seed file = bin/rails db:seed [OK]

Hint: Run seeds with bin/rails db:seed command [OK]

Common Mistakes:

• Using rails generate seed instead of db:seed
• Confusing db:create with db:seed
• Trying to run seeds with rails server

3. Given this seed code in db/seeds.rb:

3.times do |i|
  User.create(name: "User #{i + 1}")
end

What will be the names of the users created after running bin/rails db:seed?

medium

A. ["User 1", "User 2"]

B. ["User 0", "User 1", "User 2"]

C. ["User 1", "User 2", "User 3"]

D. ["User 3", "User 2", "User 1"]

Solution

1. Step 1: Understand the loop and index

   The loop runs 3 times with i values 0, 1, 2.

2. Step 2: Calculate user names

   Each user name is "User " plus i + 1, so names are "User 1", "User 2", "User 3".

3. Final Answer:

   ["User 1", "User 2", "User 3"] -> Option C

4. Quick Check:

   Loop 3 times with i+1 = User 1, 2, 3 [OK]

Hint: Remember loop index starts at 0, add 1 for names [OK]

Common Mistakes:

• Using i without adding 1, causing off-by-one names
• Assuming loop runs 2 times instead of 3
• Mixing order of names

4. What is wrong with this seed code snippet?

User.create(name: "Alice")
User.create(name: "Bob")
User.create(name: )

medium

A. Missing value for name in the last User.create call

B. User.create cannot be called multiple times

C. Names must be unique, so this will fail

D. The code should be inside a loop

Solution

1. Step 1: Check syntax of each User.create call

   The first two calls have valid name values. The last call has name: with no value, which is a syntax error.

2. Step 2: Verify other options

   Calling User.create multiple times is allowed. Names do not have to be unique unless validated. Loop is optional.

3. Final Answer:

   Missing value for name in the last User.create call -> Option A

4. Quick Check:

   Empty value after name: causes syntax error [OK]

Hint: Check for missing values after keys in hashes [OK]

Common Mistakes:

• Thinking multiple create calls are invalid
• Assuming uniqueness is required by default
• Believing loops are mandatory for seeds

5. You want to seed your database with categories but only if they don't already exist. Which seed code snippet correctly does this?

hard

A. ['Books', 'Movies', 'Music'].each do |name|
Category.find_or_create_by(name: name)
end

B. ['Books', 'Movies', 'Music'].each do |name|
Category.create(name: name)
end

C. Category.delete_all
['Books', 'Movies', 'Music'].each do |name|
Category.create(name: name)
end

D. Category.create(['Books', 'Movies', 'Music'])

Solution

1. Step 1: Understand the requirement to avoid duplicates

   We want to add categories only if they don't exist yet, so we must check before creating.

2. Step 2: Analyze each option

   ['Books', 'Movies', 'Music'].each do |name| Category.create(name: name) end always creates new records, causing duplicates. ['Books', 'Movies', 'Music'].each do |name| Category.find_or_create_by(name: name) end uses find_or_create_by which checks existence before creating. Category.delete_all ['Books', 'Movies', 'Music'].each do |name| Category.create(name: name) end deletes all categories first, which is destructive. Category.create(['Books', 'Movies', 'Music']) tries to create with an array directly, which is invalid syntax.

3. Final Answer:

   ['Books', 'Movies', 'Music'].each do |name| Category.find_or_create_by(name: name) end -> Option A

4. Quick Check:

   Use find_or_create_by to avoid duplicates [OK]

Hint: Use find_or_create_by to prevent duplicate seed entries [OK]

Common Mistakes:

• Creating records without checking duplicates
• Deleting all data before seeding unnecessarily
• Passing array directly to create without hashes