Performance profiling basics in Ruby - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to require the Ruby profiler library.

Ruby

require '[1]'

Drag options to blanks, or click blank then click option'

Aperformance

Bprofiler

Cprofile

Dbenchmark

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'profiler' instead of 'profile' causes a load error.

Using 'benchmark' is for timing, not profiling.

The Ruby standard library for profiling code is called profile. You need to require it to use profiling features.

2fill in blank

medium

Complete the code to start profiling a block of code.

Ruby

[1] do
  sleep(1)
end

Drag options to blanks, or click blank then click option'

AProfile.profile

BProfiler.profile

CProfile do

Dprofile do

Attempts:

3 left

💡 Hint

Common Mistakes

Using Profiler instead of Profile causes an error.

Omitting .profile or using lowercase module name causes errors.

Not using 'do' to start the block causes syntax errors.

The Profile.profile method is used with a block to profile the code inside. It must be capitalized Profile and lowercase profile method, used with do to start the block. This convenience method handles start, run block, stop, and print_profile automatically.

3fill in blank

hard

Fix the error in the code to correctly profile a method execution.

Ruby

require 'profile'

def slow_method
  sleep(2)
end

[1]

Drag options to blanks, or click blank then click option'

AProfile.profile { slow_method }

BProfile.profile

CProfile.profile {

DProfile.profile do

Attempts:

3 left

💡 Hint

Common Mistakes

Calling Profile.profile slow_method without a block causes an error.

Incomplete block syntax like missing } or end causes syntax errors.

The Profile.profile method expects a block. You must pass the method call inside a block using curly braces { slow_method } or do...end.

4fill in blank

hard

Fill both blanks to create a hash that stores method names and their execution times.

Ruby

times = { [1] => 1.2, [2] => 0.5 }

Drag options to blanks, or click blank then click option'

A:slow_method

B:fast_method

C:average_method

D:quick_method

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings instead of symbols for keys.

Mixing unrelated method names and times.

We use symbols as keys to represent method names. Here, :slow_method and :fast_method are used as keys with their execution times as values.

5fill in blank

hard

Fill all three blanks to filter and print methods with execution time greater than 1 second.

Ruby

times.select { |[1], [2]| [2] [3] 1 }.each do |method, time|
  puts "Method: #{method}, Time: #{time}s"
end

Drag options to blanks, or click blank then click option'

Amethod

Btime

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the block variables causes wrong filtering.

Using '<' instead of '>' filters the wrong methods.

The block variables are method and time. We filter with time > 1 to get methods taking more than 1 second.

Practice

1. What is the main purpose of performance profiling in Ruby?

easy

A. To find slow parts of the code that need optimization

B. To add new features to the Ruby program

C. To check syntax errors in the code

D. To convert Ruby code into another language

Solution

1. Step 1: Understand the goal of profiling

   Performance profiling is used to measure how long parts of code take to run.

2. Step 2: Identify the main use

   It helps find slow parts so you can improve them.

3. Final Answer:

   To find slow parts of the code that need optimization -> Option A

4. Quick Check:

   Profiling = Find slow code [OK]

Hint: Profiling = finding slow code parts to speed up [OK]

Common Mistakes:

• Confusing profiling with debugging syntax errors
• Thinking profiling adds features
• Believing profiling translates code

2. Which Ruby gem is commonly used for performance profiling?

easy

A. nokogiri

B. rails

C. ruby-prof

D. rspec

Solution

1. Step 1: Recall common Ruby gems

   Rails is a web framework, Nokogiri is for XML/HTML parsing, RSpec is for testing.

2. Step 2: Identify profiling gem

   ruby-prof is the gem designed for performance profiling.

3. Final Answer:

   ruby-prof -> Option C

4. Quick Check:

   Profiling gem = ruby-prof [OK]

Hint: ruby-prof gem is for profiling Ruby code [OK]

Common Mistakes:

• Choosing Rails as a profiling tool
• Confusing testing gem RSpec with profiling
• Picking unrelated gems like Nokogiri

3. Given this Ruby profiling output snippet:

Method       | Total Time | Self Time
calculate    | 0.50       | 0.40
process      | 0.30       | 0.10
render       | 0.20       | 0.20

Which method should you optimize first to improve performance?

medium

A. calculate

B. render

C. All methods equally

D. process

Solution

1. Step 1: Understand self time meaning

   Self time shows how much time the method itself takes, excluding calls to others.

2. Step 2: Compare self times

   calculate has the highest self time (0.40), so it is the slowest part to optimize.

3. Final Answer:

   calculate -> Option A

4. Quick Check:

   Highest self time = calculate [OK]

Hint: Optimize method with highest self time first [OK]

Common Mistakes:

• Choosing method with highest total time instead of self time
• Thinking all methods need equal optimization
• Ignoring self time importance

4. What is wrong with this Ruby profiling code snippet?

require 'ruby-prof'
ruby-prof.start
# some code here
result = RubyProf.stop
puts result

medium

A. Missing require statement for ruby-prof

B. Not starting the profiler before code

C. No code to profile

D. Using puts directly on result object

Solution

1. Step 1: Check require and start

   require 'ruby-prof' and ruby-prof.start are correctly used.

2. Step 2: Understand result object usage

   result is a RubyProf::Profile object; printing it directly with puts won't show readable output.

3. Final Answer:

   Using puts directly on result object -> Option D

4. Quick Check:

   Print profiling result properly, not with puts [OK]

Hint: Use printer classes to display profiling results, not puts [OK]

Common Mistakes:

• Printing result object directly
• Forgetting to start profiler
• Not requiring ruby-prof gem

5. You want to profile a Ruby method heavy_task and save the results to a file in a readable format. Which code snippet correctly does this?

hard

A. require 'ruby-prof'
ruby-prof.start
heavy_task
result = RubyProf.stop
File.open('profile.txt', 'w') { |f| f.puts result }

B. require 'ruby-prof'
ruby-prof.start
heavy_task
result = RubyProf.stop
printer = RubyProf::FlatPrinter.new(result)
File.open('profile.txt', 'w') { |f| printer.print(f) }

C. require 'ruby-prof'
result = RubyProf.profile { heavy_task }
File.write('profile.txt', result.to_s)

D. require 'ruby-prof'
ruby-prof.start
heavy_task
result = RubyProf.stop
puts result.to_s > 'profile.txt'

Solution

1. Step 1: Understand profiling and printing

   ruby-prof returns a result object that needs a printer to format output.

2. Step 2: Check each option for correct usage

   require 'ruby-prof' ruby-prof.start heavy_task result = RubyProf.stop printer = RubyProf::FlatPrinter.new(result) File.open('profile.txt', 'w') { |f| printer.print(f) } uses FlatPrinter to format and writes to file correctly. require 'ruby-prof' ruby-prof.start heavy_task result = RubyProf.stop File.open('profile.txt', 'w') { |f| f.puts result } writes raw object, require 'ruby-prof' result = RubyProf.profile { heavy_task } File.write('profile.txt', result.to_s) misuses to_s, require 'ruby-prof' ruby-prof.start heavy_task result = RubyProf.stop puts result.to_s > 'profile.txt' misuses puts redirection.

3. Final Answer:

   Option B code snippet -> Option B

4. Quick Check:

   Use printer to save profiling output [OK]

Hint: Use RubyProf printers to save readable profiling results [OK]

Common Mistakes:

• Writing raw result object to file
• Using puts with redirection incorrectly
• Not using a printer to format output