Sequence vs collection performance in Kotlin - Hands-On Comparison

Sequence vs Collection Performance in Kotlin

📖 Scenario: You are working on a Kotlin program that processes a list of numbers. You want to understand how using Sequence compares to using a regular List in terms of performance when filtering and mapping data.

🎯 Goal: Build a Kotlin program that creates a list of numbers, sets up a threshold value, applies filtering and mapping using both List and Sequence, and completes the code to compare their usage.

📋 What You'll Learn

Create a List of integers from 1 to 10

Create a threshold variable called threshold with value 5

Use filter and map on the List to get numbers greater than threshold and multiply them by 2

Use asSequence() on the List and apply the same filter and map operations

Convert the Sequence back to a List to complete the processing

💡 Why This Matters

🌍 Real World

Processing large collections of data efficiently is common in apps, and sequences help by doing operations lazily.

💼 Career

Understanding sequences vs collections is important for Kotlin developers to write efficient and clean code.

1

Create the initial list of numbers

Create a List called numbers containing the integers from 1 to 10.

Kotlin

# Your code here

Hint

Use listOf to create a list with the exact numbers 1 through 10.

2

Add a threshold variable

Create an integer variable called threshold and set it to 5.

Kotlin

val numbers = listOf(1, 2, 3, 4, 5, 6, 7, 8, 9, 10)
# Your code here

Hint

Just create a variable named threshold and assign it the value 5.

3

Filter and map the list

Create a new List called filteredMappedList by filtering numbers to keep only values greater than threshold and then mapping each remaining number to its double (multiply by 2).

Kotlin

val numbers = listOf(1, 2, 3, 4, 5, 6, 7, 8, 9, 10)
val threshold = 5
# Your code here

Hint

Use filter with a lambda checking it > threshold, then map to multiply by 2.

4

Use Sequence to filter and map

Create a new List called filteredMappedSequence by converting numbers to a Sequence using asSequence(), then applying the same filter and map operations, and finally converting the result back to a List.

Kotlin

val numbers = listOf(1, 2, 3, 4, 5, 6, 7, 8, 9, 10)
val threshold = 5
val filteredMappedList = numbers.filter { it > threshold }.map { it * 2 }
# Your code here

Hint

Use asSequence() on numbers, then filter and map, and finally toList().

Practice

1. What is the main advantage of using a Sequence over a Collection in Kotlin when working with large datasets?

easy

A. Sequences process data lazily, saving memory and improving performance.

B. Sequences store all data in memory for faster access.

C. Sequences automatically sort data for you.

D. Sequences are easier to write than collections.

Solution

1. Step 1: Understand how sequences process data

   Sequences process elements one by one only when needed, which is called lazy processing.

2. Step 2: Compare with collections

   Collections hold all elements in memory and process them eagerly, which can use more memory for large data.

3. Final Answer:

   Sequences process data lazily, saving memory and improving performance. -> Option A

4. Quick Check:

   Lazy processing = better for large data [OK]

Hint: Remember: sequences delay work, collections do it all at once [OK]

Common Mistakes:

• Thinking sequences store all data in memory
• Confusing lazy processing with sorting
• Assuming sequences are always simpler to write

2. Which of the following Kotlin code snippets correctly creates a sequence from a list?

easy

A. val seq = listOf(1, 2, 3).toSequence()

B. val seq = sequenceOf(listOf(1, 2, 3))

C. val seq = listOf(1, 2, 3).asSequence()

D. val seq = Sequence(listOf(1, 2, 3))

Solution

1. Step 1: Identify correct method to convert list to sequence

   The method asSequence() converts a collection to a sequence lazily.

2. Step 2: Check other options for correctness

   sequenceOf() creates a sequence from given elements, not a list; toSequence() and Sequence() constructor do not exist.

3. Final Answer:

   val seq = listOf(1, 2, 3).asSequence() -> Option C

4. Quick Check:

   Use asSequence() to convert collections [OK]

Hint: Use asSequence() to convert collections to sequences [OK]

Common Mistakes:

• Using non-existent toSequence() method
• Confusing sequenceOf() with asSequence()
• Trying to call Sequence() constructor directly

3. Consider the following Kotlin code:

val numbers = (1..5).asSequence()
    .map { it * 2 }
    .filter { it > 5 }
    .toList()
println(numbers)

What is the output?

medium

A. [12, 14, 16]

B. [2, 4, 6, 8, 10]

C. [1, 2, 3, 4, 5]

D. [6, 8, 10]

Solution

1. Step 1: Apply map transformation

   Numbers 1 to 5 are doubled: [2, 4, 6, 8, 10].

2. Step 2: Apply filter condition

   Keep only numbers greater than 5: [6, 8, 10].

3. Final Answer:

   [6, 8, 10] -> Option D

4. Quick Check:

   Map then filter = [6, 8, 10] [OK]

Hint: Map first, then filter to get final list [OK]

Common Mistakes:

• Filtering before mapping
• Forgetting to convert sequence to list
• Assuming original range is unchanged

4. What is wrong with this Kotlin code snippet?

val list = listOf(1, 2, 3, 4, 5)
val seq = list.asSequence()
val result = seq.map { it * 2 }
println(result)

medium

A. The map function does not exist for sequences.

B. The map operation is not executed because sequences are lazy.

C. The println statement causes a syntax error.

D. You cannot convert a list to a sequence using asSequence().

Solution

1. Step 1: Understand sequence laziness

   Sequences process operations lazily, so map returns a sequence but does not execute immediately.

2. Step 2: Check what is printed

   Printing result prints the sequence object, not the transformed data, because no terminal operation like toList() was called.

3. Final Answer:

   The map operation is not executed because sequences are lazy. -> Option B

4. Quick Check:

   Sequences need terminal operation to execute [OK]

Hint: Call toList() or similar to execute sequence operations [OK]

Common Mistakes:

• Expecting immediate execution of map on sequences
• Thinking asSequence() is invalid
• Assuming println shows transformed data

5. You have a large database query result as a Kotlin list of 1 million records. You want to filter records where age > 30, then map to names, and finally collect the first 10 names. Which approach is best for performance?

hard

A. Use a sequence: convert list to sequence, filter, map, then take(10) and toList().

B. Use a collection: filter, map on the list, then take first 10 elements.

C. Convert list to array, then filter and map using loops.

D. Sort the list first, then filter and map.

Solution

1. Step 1: Consider data size and operations

   With 1 million records, processing eagerly wastes memory and time.

2. Step 2: Use sequence for lazy processing

   Sequence processes elements one by one, stops after taking 10, saving resources.

3. Step 3: Compare other options

   Collections process all data eagerly; arrays and sorting add unnecessary overhead.

4. Final Answer:

   Use a sequence: convert list to sequence, filter, map, then take(10) and toList(). -> Option A

5. Quick Check:

   Lazy sequence + take(10) = best for large data [OK]

Hint: Use sequences with take() to limit processing early [OK]

Common Mistakes:

• Processing entire list eagerly wasting memory
• Sorting unnecessarily before filtering
• Using arrays without lazy evaluation