Running and rolling back migrations in Ruby on Rails - Performance & Optimization

Performance: Running and rolling back migrations

MEDIUM IMPACT

This concept affects the database schema update speed and application startup time during deployment.

Updating database schema during deployment

Ruby on Rails

rails db:migrate

Runs only pending migrations, reducing downtime and database locking.

📈 Performance Gainreduces blocking time to only necessary schema changes

Updating database schema during deployment

Ruby on Rails

rails db:migrate:reset

Running all migrations every time can cause unnecessary delays and locks if many migrations exist.

📉 Performance Costblocks deployment for several seconds to minutes depending on migration count

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Running all migrations every deploy	N/A	N/A	N/A	[X] Bad
Running only pending migrations	N/A	N/A	N/A	[OK] Good
Rolling back many migrations at once	N/A	N/A	N/A	[X] Bad
Rolling back one migration at a time	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Migrations affect backend database state and indirectly impact frontend load by controlling schema readiness. Running or rolling back migrations triggers database schema changes that can lock tables and delay queries.

→Database Locking

→Query Execution

→App Startup

⚠️ BottleneckDatabase Locking during migration execution

Optimization Tips

1Run only pending migrations to reduce deployment blocking.

2Keep migrations small and fast to minimize database locks.

3Rollback migrations incrementally to avoid long lock durations.

Performance Quiz - 3 Questions

What is the performance impact of running all migrations every deployment?

A It causes unnecessary delays and database locks.

B It speeds up deployment by preloading all migrations.

C It has no impact on deployment speed.

D It reduces database locking by batching migrations.

DevTools: Rails Console and Logs

How to check: Monitor migration execution time and database locks via logs and Rails console commands like 'SHOW PROCESSLIST' in MySQL or 'pg_stat_activity' in PostgreSQL.

What to look for: Long-running migration queries or locks that block other database operations indicate performance issues.