Why custom exceptions are needed in Java - Performance Analysis

Time Complexity: Why custom exceptions are needed

O(n)

Understanding Time Complexity

We want to understand how the time cost changes when using custom exceptions in Java.

How does adding custom exceptions affect the program's running time as input grows?

Scenario Under Consideration

Analyze the time complexity of this code snippet using a custom exception.

public class CustomException extends Exception {
    public CustomException(String message) {
        super(message);
    }
}

public void checkValue(int value) throws CustomException {
    if (value < 0) {
        throw new CustomException("Negative value not allowed");
    }
}
    

This code defines a custom exception and throws it when a value is negative.

Identify Repeating Operations

Look for repeated checks or exception throws.

• Primary operation: Checking the value and possibly throwing the exception.
• How many times: Once per call to checkValue.

How Execution Grows With Input

Each time we call checkValue, it does one check and maybe throws an exception.

Input Size (n)	Approx. Operations
10	10 checks, some exceptions
100	100 checks, some exceptions
1000	1000 checks, some exceptions

Pattern observation: The number of operations grows directly with the number of calls.

Final Time Complexity

Time Complexity: O(n)

This means the time grows linearly with how many times you check values and possibly throw exceptions.

Common Mistake

[X] Wrong: "Using custom exceptions makes the program slower in a way that grows faster than linearly."

[OK] Correct: Each exception check is simple and happens once per call, so time grows linearly, not faster.

Interview Connect

Understanding how custom exceptions affect time helps you explain your code's behavior clearly and confidently in interviews.

Self-Check

What if we added a loop inside checkValue that checks multiple values before throwing an exception? How would the time complexity change?