Value type vs reference type performance in C Sharp (C#) - Hands-On Comparison

Value type vs reference type performance

📖 Scenario: Imagine you want to compare how fast two types of data containers work in C#: one that stores data directly (value type) and one that stores a reference to data (reference type). This helps understand how choosing the right type affects your program's speed.

🎯 Goal: You will create a simple program that measures and compares the time taken to add numbers using a struct (value type) and a class (reference type).

📋 What You'll Learn

Create a struct named ValueNumber with an int field called Number.

Create a class named ReferenceNumber with an int field called Number.

Create a variable count set to 1000000 to control the number of repetitions.

Write two loops: one that sums Number from ValueNumber instances, and one that sums Number from ReferenceNumber instances.

Measure and print the time taken for each loop.

💡 Why This Matters

🌍 Real World

Understanding value vs reference types helps write faster and more efficient programs, especially in games, simulations, or apps processing large data.

💼 Career

Many software development jobs require knowledge of how data types affect performance and memory usage to optimize applications.

1

Create value and reference types

Create a struct called ValueNumber with an int field named Number. Also create a class called ReferenceNumber with an int field named Number.

C Sharp (C#)

// Your code here

Hint

Use struct for ValueNumber and class for ReferenceNumber. Both should have a public int Number field.

2

Set up count variable

Create an int variable named count and set it to 1000000.

C Sharp (C#)

struct ValueNumber
{
    public int Number;
}

class ReferenceNumber
{
    public int Number;
}

// Your code here

Hint

Use int count = 1000000; to set the number of repetitions.

3

Sum numbers using value and reference types

Create a for loop from 0 to count that sums the Number field of ValueNumber instances. Then create another for loop from 0 to count that sums the Number field of ReferenceNumber instances. Use variables valueSum and referenceSum to store the sums.

C Sharp (C#)

struct ValueNumber
{
    public int Number;
}

class ReferenceNumber
{
    public int Number;
}

int count = 1000000;

// Your code here

Hint

Use two separate for loops. In each, create a new instance and add its Number to the sum variable.

4

Measure and print execution time

Use System.Diagnostics.Stopwatch to measure the time taken by each loop. Print the elapsed milliseconds for value type sum with "Value type time: " and for reference type sum with "Reference type time: ".

C Sharp (C#)

struct ValueNumber
{
    public int Number;
}

class ReferenceNumber
{
    public int Number;
}

int count = 1000000;

// Your code here

Hint

Use Stopwatch to time each loop separately. Print the results with Console.WriteLine including the labels exactly as shown.

Practice

1. Which of the following is true about value types in C#?

easy

A. They cannot be used with primitive data like int or bool.

B. They store a reference to the data on the heap.

C. They are always slower than reference types.

D. They store data directly and are generally faster for small data.

Solution

1. Step 1: Understand value type storage

   Value types store the actual data directly, usually on the stack, which makes access faster for small data.

2. Step 2: Compare with reference types

   Reference types store a pointer to data on the heap, which involves extra memory access and can be slower.

3. Final Answer:

   They store data directly and are generally faster for small data. -> Option D

4. Quick Check:

   Value types = direct data storage [OK]

Hint: Value types hold data directly, making them faster for small data [OK]

Common Mistakes:

• Confusing value types with reference types
• Thinking value types always slower
• Believing value types cannot hold primitives

2. Which syntax correctly declares a value type variable in C#?

easy

A. int number = 10;

B. string text = "hello";

C. MyClass obj = new MyClass();

D. var list = new List<int>();

Solution

1. Step 1: Identify value type declaration

   In C#, int is a value type and int number = 10; declares it correctly.

2. Step 2: Check other options

   string, MyClass, and List<int> are reference types, so they are incorrect for value types.

3. Final Answer:

   int number = 10; -> Option A

4. Quick Check:

   int is value type declaration [OK]

Hint: Value types use simple types like int, double, bool [OK]

Common Mistakes:

• Choosing string as value type
• Confusing class instances with value types
• Using var without clear type

3. What is the output of this C# code?

struct Point { public int X; public int Y; }
Point p1 = new Point { X = 5, Y = 10 };
Point p2 = p1;
p2.X = 20;
Console.WriteLine(p1.X);

medium

A. 20

B. 0

C. 5

D. Compilation error

Solution

1. Step 1: Understand struct copying behavior

   Structs are value types, so p2 = p1; copies the data, not the reference.

2. Step 2: Analyze modification effect

   Changing p2.X to 20 does not affect p1.X, which remains 5.

3. Final Answer:

   5 -> Option C

4. Quick Check:

   Value type copy keeps original unchanged [OK]

Hint: Struct assignment copies data, original stays same [OK]

Common Mistakes:

• Assuming structs behave like reference types
• Expecting p1.X to change after p2.X changes
• Confusing struct with class behavior

4. Identify the error in this code related to value and reference types:

class MyClass { public int Value; }
MyClass a = new MyClass();
MyClass b = a;
b.Value = 10;
Console.WriteLine(a.Value);

medium

A. No error; output is 10 because both refer to same object.

B. Error: Cannot assign one class instance to another.

C. Error: Value types cannot be assigned like this.

D. Output is 0 because b.Value change does not affect a.Value.

Solution

1. Step 1: Understand reference type assignment

   Classes are reference types, so b = a; makes both variables point to the same object.

2. Step 2: Analyze output after modification

   Changing b.Value to 10 changes the object, so a.Value also shows 10.

3. Final Answer:

   No error; output is 10 because both refer to same object. -> Option A

4. Quick Check:

   Reference types share object, changes reflect [OK]

Hint: Class variables point to same object, changes affect both [OK]

Common Mistakes:

• Thinking class assignment copies data
• Expecting separate copies for reference types
• Confusing value and reference type behavior

5. You want to improve performance by reducing heap allocations in a C# program that uses many small data objects. Which approach is best?

hard

A. Use classes everywhere to benefit from garbage collection.

B. Use structs (value types) instead of classes (reference types) for small data objects.

C. Use strings instead of structs for better speed.

D. Always box value types to improve memory usage.

Solution

1. Step 1: Identify performance impact of types

   Classes allocate objects on the heap, causing more memory overhead and garbage collection.

2. Step 2: Choose value types for small data

   Structs are value types stored on the stack, reducing heap allocations and improving speed for small objects.

3. Final Answer:

   Use structs (value types) instead of classes (reference types) for small data objects. -> Option B

4. Quick Check:

   Structs reduce heap allocations, improving performance [OK]

Hint: Use structs for small data to avoid heap overhead [OK]

Common Mistakes:

• Using classes for all data regardless of size
• Thinking boxing improves memory
• Replacing structs with strings incorrectly