LINQ performance considerations in C Sharp (C#) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to use LINQ to filter numbers greater than 10.

C Sharp (C#)

var result = numbers.Where(n => n [1] 10);

Drag options to blanks, or click blank then click option'

A==

B<

C>

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' will select numbers less than 10, which is incorrect.

Using '==' selects only numbers equal to 10, not greater.

The 'Where' method filters elements. Using '>' selects numbers greater than 10.

2fill in blank

medium

Complete the code to convert the filtered result to a list for better performance.

C Sharp (C#)

var list = result.[1]();

Drag options to blanks, or click blank then click option'

AWhere

BToArray

CSelect

DToList

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Where' again does not materialize the query.

Using 'Select' is for projection, not materialization.

Using 'ToList()' materializes the query immediately, improving performance when enumerating multiple times.

3fill in blank

hard

Fix the error in the LINQ query to avoid multiple enumerations causing performance issues.

C Sharp (C#)

var count = [1].Count();
var first = numbers.First();

Drag options to blanks, or click blank then click option'

Anumbers

Bnumbers.Select(n => n * 2)

Cnumbers.Where(n => n > 5)

Dnumbers.OrderBy(n => n)

Attempts:

3 left

💡 Hint

Common Mistakes

Using a query expression directly causes it to run multiple times.

Not materializing the query can cause performance hits.

Using 'numbers' directly avoids multiple enumerations of a query, which can be costly.

4fill in blank

hard

Fill both blanks to create a dictionary from a list with keys as IDs and values as names.

C Sharp (C#)

var dict = people.ToDictionary(p => p[1], p => p[2]);

Drag options to blanks, or click blank then click option'

A.Id

B.Name

C.Age

D.Address

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-unique fields as keys causes runtime errors.

Swapping key and value selectors leads to incorrect dictionary.

'ToDictionary' needs a key selector and a value selector. Here, keys are IDs and values are Names.

5fill in blank

hard

Fill all three blanks to create a filtered and projected list of uppercase names for people older than 30.

C Sharp (C#)

var result = people.Where(p => p[1] > 30).Select(p => p[2].[3]()).ToList();

Drag options to blanks, or click blank then click option'

A.Age

B.Name

CToUpper

DToLower

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ToLower' instead of 'ToUpper' changes the case incorrectly.

Filtering by wrong property leads to wrong results.

Filter by age > 30, select the Name property, then convert it to uppercase.

Practice

1. What is a common performance consideration when using LINQ in C#?

easy

A. LINQ automatically caches all query results.

B. LINQ always executes queries immediately when defined.

C. LINQ queries are executed only when their results are requested.

D. LINQ does not support filtering collections.

Solution

1. Step 1: Understand LINQ query execution

   LINQ uses deferred execution, meaning queries run only when results are requested.

2. Step 2: Compare options with LINQ behavior

   The statement that LINQ queries are executed only when their results are requested correctly states deferred execution. The other options are incorrect because LINQ does not cache automatically, does not execute immediately when defined, and does support filtering collections.

3. Final Answer:

   LINQ queries are executed only when their results are requested. -> Option C

4. Quick Check:

   Deferred execution = LINQ queries are executed only when their results are requested. [OK]

Hint: Remember LINQ runs queries only when you ask for results [OK]

Common Mistakes:

• Assuming LINQ runs queries immediately when defined
• Thinking LINQ caches results automatically
• Believing LINQ cannot filter collections

2. Which of the following is the correct syntax to force immediate execution of a LINQ query in C#?

easy

A. var result = query.ToList();

B. var result = query.Where(x => x > 5);

C. var result = query.Select(x => x * 2);

D. var result = query.OrderBy(x => x);

Solution

1. Step 1: Identify methods that trigger immediate execution

   Methods like ToList() force LINQ to execute immediately and return a list.

2. Step 2: Analyze each option

   var result = query.ToList(); uses ToList(), which triggers execution. Where, Select, and OrderBy return queryable objects and do not execute immediately.

3. Final Answer:

   var result = query.ToList(); -> Option A

4. Quick Check:

   ToList() triggers execution = var result = query.ToList(); [OK]

Hint: Use ToList() to run LINQ query immediately [OK]

Common Mistakes:

• Using Where, Select, or OrderBy expecting immediate execution
• Not knowing ToList() triggers execution
• Confusing query definition with execution

3. Consider the following code:

var numbers = new List<int> {1, 2, 3, 4, 5};
var query = numbers.Where(n => n > 2);
var count1 = query.Count();
var count2 = query.Count();

What is the performance implication of this code?

medium

A. The query throws an exception on second Count() call.

B. The query is executed once and cached automatically.

C. The query results are stored in a list by default.

D. The query is executed twice, causing repeated filtering.

Solution

1. Step 1: Understand deferred execution and repeated calls

   Each call to Count() on a LINQ query triggers execution, so query runs twice here.

2. Step 2: Analyze caching behavior

   LINQ does not cache results automatically, so repeated calls cause repeated work.

3. Final Answer:

   The query is executed twice, causing repeated filtering. -> Option D

4. Quick Check:

   Repeated calls rerun query = The query is executed twice, causing repeated filtering. [OK]

Hint: Repeated calls rerun LINQ unless results are cached [OK]

Common Mistakes:

• Assuming LINQ caches results automatically
• Thinking Count() returns cached value on second call
• Believing query throws exceptions on multiple calls

4. Identify the performance issue in this code snippet:

var data = Enumerable.Range(1, 1000);
var filtered = data.Where(x => x % 2 == 0);
var list1 = filtered.ToList();
var list2 = filtered.ToList();

medium

A. The filtered query is executed twice, causing duplicate work.

B. ToList() does not execute the query.

C. The Where clause is ignored due to deferred execution.

D. Enumerable.Range creates an empty collection.

Solution

1. Step 1: Understand ToList() effect on query execution

   Each ToList() call executes the query fully, so filtered runs twice here.

2. Step 2: Identify repeated execution impact

   Repeated execution wastes resources; caching results in a variable avoids this.

3. Final Answer:

   The filtered query is executed twice, causing duplicate work. -> Option A

4. Quick Check:

   Multiple ToList() calls rerun query = The filtered query is executed twice, causing duplicate work. [OK]

Hint: Cache ToList() result to avoid running query twice [OK]

Common Mistakes:

• Thinking ToList() does not execute query
• Believing Where clause is ignored
• Assuming Enumerable.Range creates empty list

5. You have a LINQ query that filters and sorts a large collection multiple times in your code. What is the best way to improve performance?

hard

A. Rewrite the query each time to ensure fresh data is processed.

B. Store the filtered and sorted results in a list once, then reuse that list.

C. Avoid using ToList() to keep queries deferred for better performance.

D. Use multiple Where clauses instead of combining filters.

Solution

1. Step 1: Recognize repeated query execution cost

   Running the same LINQ query multiple times causes repeated filtering and sorting, which is expensive.

2. Step 2: Apply caching to improve performance

   Storing results in a list with ToList() once and reusing it avoids repeated work and improves speed.

3. Final Answer:

   Store the filtered and sorted results in a list once, then reuse that list. -> Option B

4. Quick Check:

   Caching query results = Store the filtered and sorted results in a list once, then reuse that list. [OK]

Hint: Cache query results with ToList() to reuse and save time [OK]

Common Mistakes:

• Re-running queries multiple times without caching
• Avoiding ToList() thinking deferred is always faster
• Splitting filters unnecessarily causing overhead