0% completed
In many problems dealing with an array (or a LinkedList), we are asked to find or calculate something among all the subarrays (or sublists) of a given size. For example, take a look at this problem:
Given an array, find the average of each subarray of âKâ contiguous elements in it.
Let's understand this problem with an example:
Array: [1, 3, 2, 6, -1, 4, 1, 8, 2], K=5
Here, we are asked to find the average of all subarrays of '5' contiguous elements in the given array. Let's solve this:
- For the first 5 numbers (subarray from index 0-4), the average is: (1+3+2+6-1)/5 => 2.2
- The average of next 5 numbers (subarray from index 1-5) is: (3+2+6-1+4)/5 => 2.8
- For the next 5 numbers (subarray from index 2-6), the average is: (2+6-1+4+1)/5 => 2.4
...
Here is the final output containing the averages of all subarrays of size 5:
Output: [2.2, 2.8, 2.4, 3.6, 2.8]
A brute-force algorithm will calculate the sum of every 5-element subarray of the given array and divide the sum by '5' to find the average. This is what the algorithm will look like:
- Time Complexity
-
Outer loop: The outer loop runs for each possible starting index of a subarray of size
K
. Since the array hasN
elements, the outer loop runs N - K + 1 times, which is approximately O(N). -
Inner loop: For each iteration of the outer loop, the inner loop runs for
K
elements to calculate the sum of the subarray. Since the inner loop runs K times for each iteration of the outer loop, the total time complexity is O(N \times K). -
Overall time complexity: O(N \times K).
-
Can we find a better solution? Do you see any inefficiency in the above approach?
The inefficiency is that for any two consecutive subarrays of size '5', the overlapping part (which will contain four elements) will be evaluated twice. For example, take the above-mentioned input:

As you can see, there are four overlapping elements between the subarray (indexed from 0-4) and the subarray (indexed from 1-5). Can we somehow reuse the sum
we have calculated for the overlapping elements?
The efficient way to solve this problem would be to visualize each subarray as a sliding window of '5' elements. This means that we will slide the window by one element when we move on to the next subarray. To reuse the sum
from the previous subarray, we will subtract the element going out of the window and add the element now being included in the sliding window. This will save us from going through the whole subarray to find the sum
and, as a result, the algorithm complexity will reduce to O(N).

Here is the algorithm for the Sliding Window approach:
Complexity Analysis
Time Complexity
-
Single pass: The algorithm only requires one pass through the array to calculate the sum of subarrays of size
K
. The loop runs for each element of the array, so the time complexity is O(N), whereN
is the number of elements in the array. -
Sliding window: The sliding window approach ensures that we add a new element to the sum and subtract the outgoing element in constant time, O(1). As a result, for each subarray of size
K
, we perform constant-time operations. This avoids the need to re-calculate the sum for overlapping subarrays repeatedly, making it much more efficient than the nested loop approach.
Overall time complexity: O(N).
Space Complexity
-
Result array: The result array requires N - K + 1 space to store the averages of all possible subarrays of size
K
, which is approximately O(N) space. -
Additional variables: The algorithm uses a few extra variables, such as
windowSum
,windowStart
, andwindowEnd
, which take constant space, O(1).
Overall space complexity: O(N).
In the following chapters, we will apply the Sliding Window approach to solve a few problems.
In some problems, the size of the sliding window is not fixed. We have to expand or shrink the window based on the problem constraints. We will see a few examples of such problems in the next chapters.
Let's jump onto our first problem and apply the Sliding Window pattern.
.....
.....
.....
Table of Contents
Contents are not accessible
Contents are not accessible
Contents are not accessible
Contents are not accessible
Contents are not accessible