Creating a gem basics in Ruby - Performance & Efficiency

Time Complexity: Creating a gem basics

O(n)

Understanding Time Complexity

When creating a Ruby gem, it's important to understand how the time your code takes grows as it runs. This helps you know if your gem will stay fast as it handles more work.

We want to see how the time needed changes when the gem does its main tasks.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

module SimpleGem
  def self.process_items(items)
    results = []
    items.each do |item|
      results << item * 2
    end
    results
  end
end
    

This code defines a simple gem method that doubles each item in a list and returns the new list.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each item in the input list.
• How many times: Once for every item in the list.

How Execution Grows With Input

As the list gets bigger, the time to double all items grows in a straight line.

Input Size (n)	Approx. Operations
10	10
100	100
1000	1000

Pattern observation: Doubling the input size doubles the work needed.

Final Time Complexity

Time Complexity: O(n)

This means the time grows directly with the number of items you give the gem.

Common Mistake

[X] Wrong: "The gem processes all items instantly no matter how many there are."

[OK] Correct: Each item needs to be handled one by one, so more items mean more time.

Interview Connect

Understanding how your gem's work grows with input size shows you can write code that stays efficient and reliable as it scales.

Self-Check

"What if the gem method called another method inside the loop that also loops over the entire list? How would the time complexity change?"