0 1 Knapsack Problem in DSA Go - Time & Space Complexity
We want to understand how the time needed to solve the 0 1 Knapsack problem grows as the number of items and the knapsack capacity increase.
How does the algorithm's work change when we add more items or increase the capacity?
Analyze the time complexity of the following code snippet.
func knapsack(weights []int, values []int, capacity int) int {
n := len(weights)
dp := make([][]int, n+1)
for i := range dp {
dp[i] = make([]int, capacity+1)
}
for i := 1; i <= n; i++ {
for w := 1; w <= capacity; w++ {
if weights[i-1] <= w {
dp[i][w] = max(dp[i-1][w], dp[i-1][w-weights[i-1]] + values[i-1])
} else {
dp[i][w] = dp[i-1][w]
}
}
}
return dp[n][capacity]
}
func max(a, b int) int {
if a > b {
return a
}
return b
}
This code solves the 0 1 Knapsack problem using a bottom-up approach with a table to store results for subproblems.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Nested loops over items and capacities filling the dp table.
- How many times: Outer loop runs n times (number of items), inner loop runs capacity times.
As we add more items or increase capacity, the work grows by multiplying these two factors.
| Input Size (n items, capacity W) | Approx. Operations |
|---|---|
| 10 items, capacity 50 | ~ 10 * 50 = 500 |
| 100 items, capacity 1000 | ~ 100 * 1000 = 100,000 |
| 1000 items, capacity 5000 | ~ 1000 * 5000 = 5,000,000 |
Pattern observation: The operations grow roughly by multiplying the number of items and the capacity.
Time Complexity: O(n * W)
This means the time needed grows proportionally to the number of items times the knapsack capacity.
[X] Wrong: "The algorithm runs in linear time O(n) because it just loops over items once."
[OK] Correct: The algorithm also loops over all capacities for each item, so the total work depends on both items and capacity, not just items.
Understanding this time complexity helps you explain how dynamic programming solves problems efficiently by breaking them into smaller parts, a skill valued in many coding challenges.
"What if we used a recursive solution without memoization? How would the time complexity change?"
Practice
Solution
Step 1: Understand the problem goal
The 0 1 Knapsack Problem tries to select items to maximize total value without exceeding the weight limit.Step 2: Identify the constraint
The constraint is the maximum weight capacity of the knapsack, so total weight must not exceed it.Final Answer:
The total value of items without exceeding the weight limit -> Option BQuick Check:
Maximize value under weight limit = The total value of items without exceeding the weight limit [OK]
- Confusing weight limit with value limit
- Thinking the problem maximizes number of items
- Ignoring the weight constraint
Solution
Step 1: Understand 2D slice creation in Go
To create a 2D slice, first create the outer slice with length n+1, then initialize each inner slice with length W+1.Step 2: Check each option
dp := make([][]int, n+1); for i := range dp { dp[i] = make([]int, W+1) } correctly creates dp with n+1 rows and W+1 columns. Options B and C have syntax errors or wrong types. dp := make([][]int, W+1); for i := range dp { dp[i] = make([]int, n+1) }" swaps dimensions incorrectly.Final Answer:
dp := make([][]int, n+1); for i := range dp { dp[i] = make([]int, W+1) } -> Option AQuick Check:
Correct 2D slice init = dp := make([][]int, n+1); for i := range dp { dp[i] = make([]int, W+1) } [OK]
- Using make with wrong parameters
- Swapping rows and columns
- Trying to declare 2D slice in one step incorrectly
package main
import "fmt"
func main() {
weights := []int{1, 3, 4}
values := []int{10, 40, 50}
W := 6
n := len(weights)
dp := make([][]int, n+1)
for i := range dp {
dp[i] = make([]int, W+1)
}
for i := 1; i <= n; i++ {
for w := 1; w <= W; w++ {
if weights[i-1] <= w {
dp[i][w] = max(dp[i-1][w], values[i-1]+dp[i-1][w-weights[i-1]])
} else {
dp[i][w] = dp[i-1][w]
}
}
}
fmt.Println(dp[n][W])
}
func max(a, b int) int {
if a > b {
return a
}
return b
}
Solution
Step 1: Trace the DP table filling
Items: (weight=1,value=10), (3,40), (4,50), capacity=6. Calculate max value for each capacity step by step.Step 2: Calculate max value for capacity 6
Choosing items 2 and 3 (weights 3+4=7) exceeds capacity, so best is items 1 and 3 (1+4=5) with value 10+50=60 or items 2 alone (40). But items 1 and 2 (1+3=4) value 10+40=50. Actually, best is items 2 and 3 separately or items 1 and 2 and 3? Check dp: max value at capacity 6 is 90 (items 2 and 3 combined is invalid, but items 1,2,3 combined weight 8 > 6). So best is items 2 and 3 separately or items 1 and 3 combined. The code outputs 90.Final Answer:
90 -> Option CQuick Check:
Max value for capacity 6 = 90 [OK]
- Adding values without checking weight limit
- Confusing indices in dp array
- Forgetting to subtract weight when adding value
for i := 1; i <= n; i++ {
for w := 1; w <= W; w++ {
if weights[i] <= w {
dp[i][w] = max(dp[i-1][w], values[i]+dp[i-1][w-weights[i]])
} else {
dp[i][w] = dp[i-1][w]
}
}
}Solution
Step 1: Identify index error in array access
Arrays weights and values are zero-indexed, but loop uses i starting from 1, so weights[i] and values[i] cause out-of-range or wrong access.Step 2: Correct indexing for zero-based arrays
Use weights[i-1] and values[i-1] to access correct elements corresponding to current item i.Final Answer:
Use weights[i-1] and values[i-1] instead of weights[i] and values[i] -> Option AQuick Check:
Fix indexing error = Use weights[i-1] and values[i-1] instead of weights[i] and values[i] [OK]
- Using 1-based indexing on zero-based slices
- Ignoring out-of-range errors
- Changing loop start incorrectly
Solution
Step 1: Calculate total weights and values for each option
Items with weights 3 and 7, total value 9: weights 3+7=10, values 5+4=9; Items with weights 2, 3, and 5, total value 8: 2+3+5=10, values 1+5+2=8; Items with weights 2 and 7, total value 5: 2+7=9, values 1+4=5; Items with weights 5 and 7, total value 6: 5+7=12 (exceeds capacity), invalid.Step 2: Choose combination with max value under capacity
Items with weights 3 and 7, total value 9 and B fit capacity 10, but Items with weights 3 and 7, total value 9 has higher value 9 vs 8. Items with weights 5 and 7, total value 6 exceeds capacity, Items with weights 2 and 7, total value 5 has lower value.Final Answer:
Items with weights 3 and 7, total value 9 -> Option DQuick Check:
Max value with capacity 10 = 9 [OK]
- Choosing items exceeding capacity
- Ignoring total value comparison
- Adding too many items without checking weight
Ready to prove it?
Pass the test and this pattern moves unknown
