LC 636: Exclusive Time of Functions
LC 636: Exclusive Time of Functions
Difficulty: Medium
Category: Stack, Parsing, Simulation
Companies: Amazon, Facebook, Google, Twitter
Problem Statement
On a single-threaded CPU, we can only execute one function at a time. When a function call starts, it’s recorded with a start timestamp. When a call ends, it’s recorded with an end timestamp. Functions can call other functions, creating a call stack.
Given an integer n representing the number of functions, and an array logs, where logs[i] represents the i-th log message formatted as "{function_id}:{"start"|"end"}:{timestamp}", return an array where each element is the exclusive time of that function.
Exclusive time is the sum of execution times for all calls to a function, excluding time spent calling other functions.
Examples
Example 1:
Input: n = 2, logs = ["0:start:0","1:start:2","1:end:5","0:end:6"]
Output: [3,4]
Explanation:
- Function 0 starts at 0 and ends at 6, taking 6 units total
- Function 0 calls function 1, which runs from 2 to 5 (3 units)
- Function 0 exclusive time: 6 - 3 = 3 units
- Function 1 exclusive time: 5 - 2 + 1 = 4 units (inclusive of end timestamp)
Example 2:
Input: n = 1, logs = ["0:start:0","0:start:2","0:end:5","0:end:6"]
Output: [3]
Explanation:
- First call: starts at 0, second call starts at 2
- Second call ends at 5 (duration 4)
- First call ends at 6 (duration 7 total, minus 4 from nested call = 3)
Example 3:
Input: n = 2, logs = ["0:start:0","0:start:2","0:end:5","1:start:6","1:end:6","0:end:7"]
Output: [4,1]
Explanation:
- Function 0: recursive calls from 0-5 (3 units) + 6-7 (1 unit) = 4 total
- Function 1: runs at timestamp 6 (1 unit)
Constraints
1 <= n <= 1001 <= logs.length <= 5000 <= function_id < n0 <= timestamp <= 10^9- No two start events will happen at the same timestamp
- No two end events will happen at the same timestamp
- Each function call has a matching start and end event
Solution Approaches
Approach 1: Stack-Based Time Tracking (Recommended)
Key Insight: Use a stack to track the current call stack. When a function starts, push it. When it ends, calculate its duration and subtract that time from its parent.
Algorithm:
- Parse each log entry to extract function ID, action (start/end), and timestamp
- Maintain a stack of active function calls
- When a function starts: push to stack
- When a function ends:
- Pop the top function and calculate its duration
- Add duration to the function’s exclusive time
- Subtract duration from the parent function (if exists) in the stack
Time Complexity: O(m) where m is the number of logs
Space Complexity: O(n) for the stack
class Solution:
def exclusiveTime(self, n: int, logs: list[str]) -> list[int]:
result = [0] * n
st = [] # [(function_id, start_time), ...]
for log in logs:
parts = log.split(':')
func_id = int(parts[0])
action = parts[1]
timestamp = int(parts[2])
if action == 'start':
# Push function to stack
st.append((func_id, timestamp))
else:
# Pop and calculate duration
funcId, startTime = st.pop()
duration = timestamp - startTime + 1 # +1 to include end timestamp
result[funcId] += duration
# Subtract from parent function
if st:
result[st[-1][0]] -= duration
return result
Approach 2: Using String Splitting for Parsing
Algorithm: Same logic but using Python string splitting for cleaner parsing.
class Solution:
def exclusiveTime(self, n: int, logs: list[str]) -> list[int]:
result = [0] * n
st = []
for log in logs:
parts = log.split(':')
func_id = int(parts[0])
isStart = (parts[1] == "start")
timestamp = int(parts[2])
if isStart:
st.append((func_id, timestamp))
else:
funcId, startTime = st.pop()
duration = timestamp - startTime + 1
result[funcId] += duration
if st:
result[st[-1][0]] -= duration
return result
Approach 3: Store Only Start Time
Algorithm: Store only the start timestamp on the stack.
class Solution:
def exclusiveTime(self, n: int, logs: list[str]) -> list[int]:
result = [0] * n
st = [] # Only store function IDs
prevTime = 0
for log in logs:
parts = log.split(':')
func_id = int(parts[0])
isStart = (parts[1] == "start")
timestamp = int(parts[2])
if isStart:
if st:
result[st[-1]] += timestamp - prevTime
st.append(func_id)
prevTime = timestamp
else:
result[st[-1]] += timestamp - prevTime + 1
st.pop()
prevTime = timestamp + 1
return result
Algorithm Analysis
Key Insights
- Nested Function Calls: The stack naturally models the call stack hierarchy
- Exclusive vs Inclusive Time: When a function calls another, the time spent in the nested call must be subtracted from the parent
- End Timestamp Inclusion: The end timestamp is inclusive in exclusive time calculation (
+1) - Parent Tracking: The stack maintains parent-child relationships
Understanding the Subtraction Logic
Function 0: starts at 0
Function 1: starts at 2
Function 1: ends at 5 (duration = 4)
Function 0: ends at 6
Without subtraction:
Function 0: 0 to 6 = 7 units (WRONG - includes nested call)
Function 1: 2 to 5 = 4 units (CORRECT)
With subtraction:
Function 0: 7 - 4 = 3 units (CORRECT)
Function 1: 4 units (CORRECT)
Implementation Details
Manual String Parsing
// Parse function ID (numeric string to int)
id = 0
while i < len(log) and log[i] != ':':
id = id * 10 + int(log[i])
i += 1
# Check for "start" or "end"
if i + 1 < len(log) and log[i + 1] == 's':
isStart = True
Stack Operations
# Start event: push function onto stack
if isStart:
st.append((id, time))
# End event: pop and calculate
else:
funcId, startTime = st.pop()
duration = time - startTime + 1
rtn[funcId] += duration
# Subtract from parent
if st:
rtn[st[-1][0]] -= duration
Edge Cases
- Single Function: Only one function, no nesting → straightforward timing
- Recursive Calls: Same function called recursively → handled by stack
- Multiple Separate Calls: Same function called at different times → duration summed
- Immediate Returns: Start and end at same timestamp → duration = 1
- Deep Nesting: Multiple levels of function calls → stack maintains hierarchy
Follow-up Questions
- What if logs could be out of order?
- How would you handle multi-threaded execution?
- What if you needed to track inclusive time instead?
- How would you detect mismatched start/end events?
Related Problems
- LC 394: Decode String - Nested structure processing
- LC 150: Evaluate Reverse Polish Notation - Stack-based evaluation
- LC 1249: Minimum Remove to Make Valid Parentheses - Stack validation
Optimization Techniques
- Stack for Hierarchy: Perfect data structure for call stack modeling
- Subtraction Trick: Efficient way to calculate exclusive time
- Inclusive Counting: End timestamp included in duration calculation
- Parent Tracking: Stack automatically maintains parent information
Code Quality Notes
- Readability: Approach 1 with manual parsing is most educational
- Maintainability: Approach 2 with stringstream is cleaner
- Performance: All approaches are O(n) time and space
- Correctness: Key insight is the subtraction from parent
This problem elegantly demonstrates how to model a call stack using a stack data structure and calculate exclusive time by tracking parent-child relationships in function calls.