String vs StringBuilder in Java - Performance Comparison

Time Complexity: String vs StringBuilder

O(n^2) for String concatenation, O(n) for StringBuilder

Understanding Time Complexity

We want to see how fast string operations run when using String and StringBuilder.

How does the time to build or change a string grow as the string gets longer?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

String result = "";
for (int i = 0; i < n; i++) {
    result += i;
}

StringBuilder sb = new StringBuilder();
for (int i = 0; i < n; i++) {
    sb.append(i);
}
String finalResult = sb.toString();
    

This code builds a string by adding numbers from 0 to n-1 using two ways: String concatenation and StringBuilder.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Adding a number to the string inside a loop.
• How many times: The loop runs n times, repeating the add operation each time.

How Execution Grows With Input

When using String concatenation, each add creates a new string copying old content, so work grows quickly.

Input Size (n)	Approx. Operations (String)	Approx. Operations (StringBuilder)
10	About 55 copies	About 10 appends
100	About 5,050 copies	About 100 appends
1000	About 500,500 copies	About 1000 appends

Pattern observation: String concatenation work grows much faster than StringBuilder as n grows.

Final Time Complexity

Time Complexity: O(n^2) for String concatenation, O(n) for StringBuilder

Using String concatenation takes much more time as the string grows, but StringBuilder stays fast and grows evenly.

Common Mistake

[X] Wrong: "Using + to add strings in a loop is always fast enough for any size."

[OK] Correct: Each + creates a new string copying all old content, so time grows very fast and slows down big loops.

Interview Connect

Knowing when to use StringBuilder shows you understand how code speed changes with input size, a key skill in programming.

Self-Check

"What if we used StringBuffer instead of StringBuilder? How would the time complexity change?"

Practice

1. Which statement best describes when to use StringBuilder instead of String in Java?

easy

A. Use StringBuilder when you need to change text many times efficiently.

B. Use StringBuilder for fixed text that never changes.

C. Use String when you want faster text modifications.

D. Use String to save memory when changing text repeatedly.

Solution

1. Step 1: Understand the nature of String and StringBuilder

   String objects are immutable, meaning they cannot be changed once created. Changing text creates new objects, which is slow and uses more memory.

2. Step 2: Identify when StringBuilder is better

   StringBuilder allows changing text without creating new objects, making it efficient for many modifications.

3. Final Answer:

   Use StringBuilder when you need to change text many times efficiently. -> Option A

4. Quick Check:

   Many changes = StringBuilder [OK]

Hint: Use StringBuilder for many text changes, String for fixed text [OK]

Common Mistakes:

• Thinking String is better for many changes
• Confusing immutability of String
• Assuming StringBuilder uses more memory always

2. Which of the following is the correct way to create a StringBuilder object with initial text "Hello"?

easy

A. StringBuilder sb = StringBuilder("Hello");

B. StringBuilder sb = "Hello";

C. StringBuilder sb = new StringBuilder[] {"Hello"};

D. StringBuilder sb = new StringBuilder("Hello");

Solution

1. Step 1: Recall the correct constructor syntax for StringBuilder

   The StringBuilder class requires the new keyword and parentheses with the initial string inside.

2. Step 2: Check each option for syntax correctness

   StringBuilder sb = new StringBuilder("Hello"); uses new StringBuilder("Hello"), which is correct. Options A, B, and D have syntax errors or wrong usage.

3. Final Answer:

   StringBuilder sb = new StringBuilder("Hello"); -> Option D

4. Quick Check:

   Use new + constructor for StringBuilder [OK]

Hint: Always use 'new StringBuilder("text")' to create StringBuilder [OK]

Common Mistakes:

• Omitting 'new' keyword
• Using assignment without constructor
• Using array syntax mistakenly

3. What is the output of this Java code?

StringBuilder sb = new StringBuilder("Hi");
sb.append("!");
sb.append(" How are you?");
System.out.println(sb.toString());

medium

A. Hi!How are you?

B. Hi How are you?

C. Hi! How are you?

D. Hi

Solution

1. Step 1: Understand what append() does on StringBuilder

   Each append() adds the given text to the end of the current StringBuilder content without spaces unless explicitly added.

2. Step 2: Trace the code execution

   Initial text is "Hi". First append adds "!" making "Hi!". Second append adds " How are you?" (with leading space), resulting in "Hi! How are you?".

3. Final Answer:

   Hi! How are you? -> Option C

4. Quick Check:

   Appends add text exactly as given [OK]

Hint: Append adds text exactly; watch spaces carefully [OK]

Common Mistakes:

• Ignoring spaces in appended strings
• Assuming append replaces text
• Printing StringBuilder object directly without toString()

4. Identify the error in this code snippet:

StringBuilder sb = new StringBuilder("Test");
sb = sb + "ing";
System.out.println(sb);

medium

A. Cannot use + operator to concatenate StringBuilder and String.

B. Missing semicolon after StringBuilder initialization.

C. StringBuilder cannot be printed directly with println.

D. StringBuilder must be declared final.

Solution

1. Step 1: Check the use of + operator with StringBuilder

   The + operator cannot be used to add a String to a StringBuilder object directly. This causes a compile-time error.

2. Step 2: Understand correct way to append text to StringBuilder

   Use sb.append("ing") to add text instead of + operator.

3. Final Answer:

   Cannot use + operator to concatenate StringBuilder and String. -> Option A

4. Quick Check:

   Use append(), not +, with StringBuilder [OK]

Hint: Use append() to add text to StringBuilder, not + [OK]

Common Mistakes:

• Trying to use + with StringBuilder
• Thinking println can't print StringBuilder
• Forgetting semicolons

5. You want to build a sentence by adding words one by one in a loop. Which approach is best for performance and why?

Option A:
String sentence = "";
for (String word : words) {
    sentence += word + " ";
}

Option B:
StringBuilder sentence = new StringBuilder();
for (String word : words) {
    sentence.append(word).append(" ");
}

hard

A. Option A is better because String is simpler to use.

B. Option B is better because StringBuilder avoids creating many new objects.

C. Both are equally efficient for building strings in loops.

D. Option A is better because it uses less memory.

Solution

1. Step 1: Analyze Option B is better because String is simpler to use. (String concatenation in loop)

   Each concatenation with += creates a new String object because Strings are immutable, causing slow performance and more memory use.

2. Step 2: Analyze Option B is better because StringBuilder avoids creating many new objects. (StringBuilder in loop)

   StringBuilder modifies the same object without creating new ones, making it faster and more memory efficient for repeated changes.

3. Final Answer:

   Option B is better because StringBuilder avoids creating many new objects. -> Option B

4. Quick Check:

   Use StringBuilder for repeated string changes in loops [OK]

Hint: Use StringBuilder in loops to build strings efficiently [OK]

Common Mistakes:

• Using String concatenation in loops thinking it's fast
• Ignoring immutability of String
• Assuming simpler code is always better