Stream vs async stream behavior in C Sharp (C#) - Performance Comparison

Time Complexity: Stream vs async stream behavior

O(n)

Understanding Time Complexity

When working with streams in C#, it's important to understand how time grows when reading data synchronously versus asynchronously.

We want to see how the program's running time changes as the amount of data increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    public async Task ReadStreamAsync(Stream stream, int bufferSize)
    {
        byte[] buffer = new byte[bufferSize];
        int bytesRead;
        while ((bytesRead = await stream.ReadAsync(buffer, 0, buffer.Length)) > 0)
        {
            // Process bytesRead
        }
    }
    

This code reads data from a stream asynchronously in chunks until all data is read.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading chunks of data repeatedly from the stream.
• How many times: The loop runs once for each chunk until the entire stream is read.

How Execution Grows With Input

As the total data size grows, the number of read operations grows proportionally.

Input Size (bytes)	Approx. Read Calls
10,000	100 (if bufferSize=100)
100,000	1,000
1,000,000	10,000

Pattern observation: The number of read calls grows linearly with the input size.

Final Time Complexity

Time Complexity: O(n)

This means the time to read the stream grows directly in proportion to the amount of data.

Common Mistake

[X] Wrong: "Async reading makes the operation faster and changes the time complexity."

[OK] Correct: Async reading helps with responsiveness but does not reduce the total amount of work, so time complexity remains linear.

Interview Connect

Understanding how synchronous and asynchronous streams behave helps you explain performance in real applications and shows you can reason about program efficiency clearly.

Self-Check

"What if we doubled the buffer size? How would the time complexity change?"

Practice

1. What is the main difference between a Stream and an async stream in C#?

easy

A. A Stream processes data synchronously, while an async stream processes data asynchronously.

B. A Stream can only read data, but an async stream can only write data.

C. A Stream is used for text data, and an async stream is used for binary data.

D. There is no difference; both work the same way.

Solution

1. Step 1: Understand Stream behavior

   A Stream reads or writes data step-by-step synchronously, blocking the thread until data is processed.

2. Step 2: Understand async stream behavior

   An async stream uses IAsyncEnumerable<T> and await foreach to process data asynchronously, allowing other work while waiting for data.

3. Final Answer:

   A Stream processes data synchronously, while an async stream processes data asynchronously. -> Option A

4. Quick Check:

   Sync vs async processing = C [OK]

Hint: Sync streams block; async streams use await foreach [OK]

Common Mistakes:

• Thinking async streams are only for writing data
• Confusing synchronous with asynchronous processing
• Believing streams only handle text or binary exclusively

2. Which of the following is the correct syntax to consume an async stream in C#?

easy

A. foreach (var item in asyncStream) { Console.WriteLine(item); }

B. await foreach (var item in asyncStream) { Console.WriteLine(item); }

C. for await (var item in asyncStream) { Console.WriteLine(item); }

D. async foreach (var item in asyncStream) { Console.WriteLine(item); }

Solution

1. Step 1: Recall async stream consumption syntax

   Async streams require await foreach to asynchronously iterate over IAsyncEnumerable<T>.

2. Step 2: Check each option

   foreach (var item in asyncStream) { Console.WriteLine(item); } uses regular foreach which is invalid for async streams. await foreach (var item in asyncStream) { Console.WriteLine(item); } correctly uses await foreach. for await (var item in asyncStream) { Console.WriteLine(item); } uses invalid syntax for await. async foreach (var item in asyncStream) { Console.WriteLine(item); } uses invalid keyword order async foreach.

3. Final Answer:

   await foreach (var item in asyncStream) { Console.WriteLine(item); } -> Option B

4. Quick Check:

   Async stream needs await foreach = A [OK]

Hint: Use 'await foreach' to read async streams correctly [OK]

Common Mistakes:

• Using regular foreach with async streams
• Swapping 'async' and 'await' keywords incorrectly
• Trying 'for await' which is invalid in C#

3. Consider this code snippet:

async IAsyncEnumerable<int> GetNumbersAsync()
{
    for (int i = 1; i <= 3; i++)
    {
        await Task.Delay(100);
        yield return i;
    }
}

static async Task Main()
{
    await foreach (var num in GetNumbersAsync())
    {
        Console.Write(num + " ");
    }
}

What will be the output when this program runs?

medium

A. Task not awaited error

B. 123

C. 1 2 3

D. No output

Solution

1. Step 1: Understand async stream generation

   The method yields numbers 1 to 3 with a 100ms delay between each, simulating asynchronous data arrival.

2. Step 2: Understand async stream consumption

   The await foreach prints each number followed by a space as they arrive asynchronously.

3. Final Answer:

   1 2 3 -> Option C

4. Quick Check:

   Async yield with await foreach prints spaced numbers = A [OK]

Hint: Async yield returns spaced values printed by await foreach [OK]

Common Mistakes:

• Expecting numbers without spaces
• Thinking output is immediate without delay
• Confusing async stream with synchronous enumeration

4. What is wrong with this code snippet?

async IAsyncEnumerable<int> GetDataAsync()
{
    for (int i = 0; i < 3; i++)
    {
        yield return i;
        await Task.Delay(100);
    }
}

medium

A. The await must come before yield return in async streams.

B. You cannot use await after yield return in async streams.

C. The method must return IEnumerable<int> instead of IAsyncEnumerable<int>.

D. Nothing is wrong; this code is correct.

Solution

1. Step 1: Understand async stream yield rules

   In async streams, await must appear before yield return because the compiler needs to await before producing the next value.

2. Step 2: Analyze the code order

   The code yields a value first, then awaits delay, which is invalid and causes a compile error.

3. Final Answer:

   The await must come before yield return in async streams. -> Option A

4. Quick Check:

   Await before yield return in async streams = B [OK]

Hint: Await before yield return in async streams to avoid errors [OK]

Common Mistakes:

• Placing yield return before await in async streams
• Confusing return types for async streams
• Assuming no await is needed in async streams

5. You want to process a large file line-by-line without blocking your UI thread. Which approach best fits this scenario in C#?

hard

A. Use StreamReader.ReadLine() inside a synchronous foreach loop.

B. Use a regular Stream and block until all data is read.

C. Read the entire file into memory first, then process lines synchronously.

D. Use IAsyncEnumerable<string> with await foreach reading lines asynchronously.

Solution

1. Step 1: Identify UI thread blocking issue

   Reading large files synchronously blocks the UI thread, causing freezes.

2. Step 2: Choose async streaming approach

   Using IAsyncEnumerable<string> with await foreach reads lines asynchronously, allowing UI responsiveness.

3. Final Answer:

   Use IAsyncEnumerable<string> with await foreach reading lines asynchronously. -> Option D

4. Quick Check:

   Async streams keep UI responsive during file read = D [OK]

Hint: Async streams prevent UI blocking when reading large files [OK]

Common Mistakes:

• Reading files synchronously causing UI freeze
• Loading entire file into memory unnecessarily
• Using blocking Stream methods on UI thread