Puma server configuration in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding Puma's thread pool behavior

Given this Puma configuration snippet, what is the maximum number of threads Puma will use concurrently?

Ruby on Rails

threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }.to_i
threads threads_count, threads_count

A 1

B 5

C 10

D 0

💡 Hint

Look at the minimum and maximum thread counts set by the threads method.

The threads method sets both minimum and maximum threads to the same value, so Puma will use exactly 5 threads concurrently.

📝 Syntax

intermediate

Correct syntax for binding Puma to a TCP port

Which option correctly binds Puma to listen on TCP port 3000 on all interfaces?

A bind 'tcp://0.0.0.0:3000'

B bind tcp://0.0.0.0:3000

C bind 'http://0.0.0.0:3000'

D bind 'tcp:0.0.0.0:3000'

💡 Hint

The bind method expects a string with the protocol prefix.

The correct syntax requires the protocol prefix 'tcp://' inside quotes. Option A is correct.

🔧 Debug

advanced

Identify the error in Puma worker configuration

What error will this Puma configuration cause when starting the server? workers ENV.fetch("WEB_CONCURRENCY") { 2 } preload_app! on_worker_boot do ActiveRecord::Base.establish_connection end

Ruby on Rails

workers ENV.fetch("WEB_CONCURRENCY") { 2 }
preload_app!
on_worker_boot do
  ActiveRecord::Base.establish_connection
end

A No error, configuration is correct

B RuntimeError due to missing block in on_worker_boot

C SyntaxError because of missing colon after on_worker_boot

D NoMethodError because establish_connection is called without parentheses

💡 Hint

This is a standard Puma configuration for Rails applications using multiple workers.

No error; this is the recommended configuration for Puma with preload_app! and multiple workers in Rails. The establish_connection call works without parentheses as it uses the default specification.

❓ state_output

advanced

Effect of preload_app! on application state

What is the main effect of calling preload_app! in Puma configuration?

A Preloads the app after workers start, increasing memory usage

B Automatically reloads code on every request in development

C Disables worker forking and runs all requests in a single process

D Loads the application before workers fork, sharing memory and reducing startup time

💡 Hint

Think about how forking affects memory and startup speed.

preload_app! loads the app before forking workers, so memory pages can be shared, improving performance and reducing startup time.

🧠 Conceptual

expert

Choosing Puma worker count for CPU cores

If a server has 8 CPU cores and you want to optimize Puma for concurrency and memory, which worker count is best practice?

A 1 worker with 16 threads to maximize concurrency

B 16 workers, double the CPU cores for more parallelism

C 8 workers, matching the number of CPU cores

D 4 workers with 2 threads each to balance load

💡 Hint

Consider how Puma uses workers and threads relative to CPU cores.

Best practice is to set workers equal to CPU cores to maximize CPU usage without excessive context switching. Threads handle concurrency within each worker.