Production environment configuration in Ruby on Rails - Performance & Optimization

Performance: Production environment configuration

HIGH IMPACT

This affects the page load speed and runtime responsiveness by optimizing asset delivery, caching, and error handling in production.

Serving assets efficiently in production

Ruby on Rails

config.assets.compile = false
config.assets.digest = true
config.cache_classes = true
config.eager_load = true

Precompiles assets before deployment and caches classes, reducing runtime overhead and speeding up response.

📈 Performance GainReduces blocking time on requests to near zero; improves LCP and INP significantly

Serving assets efficiently in production

Ruby on Rails

config.assets.compile = true
config.assets.debug = true
config.cache_classes = false

Assets are compiled on the fly, causing slow response times and blocking rendering during requests.

📉 Performance CostBlocks rendering for hundreds of milliseconds on each request; increases server CPU usage

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
On-the-fly asset compilation	Low	Multiple on each request	High due to delayed styles/scripts	[X] Bad
Precompiled assets with caching	Low	Single initial load	Low with cached styles/scripts	[OK] Good
No compression or caching	N/A	N/A	High network payload delays paint	[X] Bad
Compression and caching enabled	N/A	N/A	Low network payload speeds paint	[OK] Good

Rendering Pipeline

Production configuration optimizes how assets and code are prepared and delivered, reducing delays in style calculation, layout, and paint stages.

→Critical Rendering Path

→Network

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork and Critical Rendering Path delays caused by on-the-fly asset compilation and lack of caching

Core Web Vital Affected

LCP, INP

This affects the page load speed and runtime responsiveness by optimizing asset delivery, caching, and error handling in production.

Optimization Tips

1Always precompile assets before deploying to production.

2Enable caching and compression to reduce payload size and speed delivery.

3Use minimal logging and disable detailed error pages in production.

Performance Quiz - 3 Questions

What is the main performance benefit of setting config.assets.compile to false in Rails production?

A Assets are ignored to speed up server response

B Assets are precompiled, reducing runtime delays and blocking

C Assets are compiled on every request for freshness

D Assets are loaded from CDN automatically

DevTools: Performance

How to check: Record a page load in production mode, then analyze the waterfall for asset loading times and scripting delays.

What to look for: Look for long blocking times during asset compilation or large uncompressed asset sizes causing slow LCP.

Practice

1. What is the main purpose of the production.rb file in a Rails application?

easy

A. To define routes for the application

B. To enable detailed error messages for debugging

C. To configure settings that optimize the app for real users, like caching and security

D. To set up the database schema

Solution

1. Step 1: Understand the role of production.rb

   This file holds configuration settings specifically for the production environment, where the app serves real users.

2. Step 2: Identify key production settings

   It disables detailed error messages and enables caching to improve speed and security.

3. Final Answer:

   To configure settings that optimize the app for real users, like caching and security -> Option C

4. Quick Check:

   Production config = optimize for real users [OK]

Hint: Production config = speed + security settings [OK]

Common Mistakes:

• Confusing production with development environment
• Thinking production shows detailed errors
• Mixing routing or database setup with production config

2. Which line correctly disables full error reports in config/environments/production.rb?

easy

A. config.consider_all_requests_local = false

B. config.show_detailed_errors = true

C. config.consider_all_requests_local = true

D. config.show_detailed_errors = false

Solution

1. Step 1: Identify the setting for error reports

   The setting consider_all_requests_local controls whether detailed error pages show.

2. Step 2: Know production default

   In production, this is set to false to hide detailed errors from users.

3. Final Answer:

   config.consider_all_requests_local = false -> Option A

4. Quick Check:

   Disable detailed errors = false [OK]

Hint: False hides errors in production [OK]

Common Mistakes:

• Setting it to true shows errors in production
• Using wrong config key like show_detailed_errors
• Confusing development and production defaults

3. Given this snippet in production.rb:

config.cache_classes = true
config.action_controller.perform_caching = true
config.assets.compile = false

What happens if you deploy without precompiling assets?

medium

A. The app will crash with a syntax error

B. Rails will compile assets on the fly, slowing down requests

C. Assets will be served normally from the public folder

D. Assets will not be served, causing missing styles and scripts

Solution

1. Step 1: Understand config.assets.compile = false

   This setting disables on-the-fly asset compilation in production.

2. Step 2: Consequence of no precompiled assets

   If assets are not precompiled, Rails cannot serve them, so styles and scripts will be missing.

3. Final Answer:

   Assets will not be served, causing missing styles and scripts -> Option D

4. Quick Check:

   No precompile + compile false = missing assets [OK]

Hint: No precompile + compile false = missing assets [OK]

Common Mistakes:

• Assuming Rails compiles assets automatically in production
• Thinking assets serve normally without precompile
• Confusing compile false with true

4. You see this error in production: ActionController::RoutingError (No route matches [GET] "/assets/application.css"). Which fix is correct?

medium

A. Precompile assets before deploying and keep config.assets.compile = false

B. Set config.assets.compile = true in production.rb

C. Remove caching settings from production.rb

D. Set config.consider_all_requests_local = true

Solution

1. Step 1: Understand the error cause

   The error means the CSS asset is missing in production, likely because assets were not precompiled.

2. Step 2: Correct fix for missing assets

   Best practice is to precompile assets before deployment and keep config.assets.compile = false for performance.

3. Final Answer:

   Precompile assets before deploying and keep config.assets.compile = false -> Option A

4. Quick Check:

   Missing assets fix = precompile + compile false [OK]

Hint: Always precompile assets for production [OK]

Common Mistakes:

• Setting compile true causes slow requests
• Removing caching does not fix missing assets
• Enabling detailed errors leaks info in production

5. You want to securely configure your Rails app for production to use environment variables for secrets and enable caching. Which combination in production.rb is best practice?

hard

A. config.cache_classes = false
config.action_controller.perform_caching = false
config.secret_key_base = ENV['SECRET_KEY_BASE']

B. config.cache_classes = true
config.action_controller.perform_caching = true
config.secret_key_base = ENV['SECRET_KEY_BASE']

C. config.cache_classes = true
config.action_controller.perform_caching = false
config.secret_key_base = 'hardcoded_secret'

D. config.cache_classes = false
config.action_controller.perform_caching = true
config.secret_key_base = 'hardcoded_secret'

Solution

1. Step 1: Identify caching and class loading best practices

   In production, cache_classes and perform_caching should be true for speed and efficiency.

2. Step 2: Use environment variables for secrets

   Secrets like secret_key_base must come from environment variables, not hardcoded strings, for security.

3. Final Answer:

   config.cache_classes = true config.action_controller.perform_caching = true config.secret_key_base = ENV['SECRET_KEY_BASE'] -> Option B

4. Quick Check:

   Caching true + env secrets = secure production [OK]

Hint: Cache true + env secrets = secure production [OK]

Common Mistakes:

• Disabling caching in production
• Hardcoding secret keys in code
• Setting cache_classes false reduces performance