Advanced C# Tips: Prefer for Loop Over foreach with Arrays

Advanced C# Tips: Prefer for Loop Over foreach with Arrays

高级 C# 技巧：对于数组，优先使用 for 循环而非 foreach

In C#, when you want to go through all the items in an array one by one, you can use either a for loop or a foreach loop. Both will get the job done, but there's a bit of a difference in how they do it, especially when it comes to performance.

在 C# 中，当你想逐个遍历数组中的所有元素时，你可以使用 for 循环或 foreach 循环。两者都能完成工作，但它们的工作方式有一些差异，尤其是在性能方面。

The for loop gives you more control. You have a counter that keeps track of which item you're on, and you can use this counter to directly access each element in the array by its index. This is a straightforward operation, and it's very fast because accessing elements by index is something arrays are designed to do efficiently.

for 循环给你更多的控制权。你有一个计数器来跟踪你正在处理哪个元素，你可以使用这个计数器通过索引直接访问数组中的每个元素。这是一个直接的操作，而且非常快，因为按索引访问元素正是数组被设计来高效完成的事情。

On the other hand, foreach is a bit more hands-off. It goes through each element for you, and it's cleaner to write since you don't have to deal with the counter or the indexing. Underneath the hood, foreach uses an enumerator object to keep track of where it is in the array. This enumerator adds a little bit of overhead because it's an extra layer between your code and the direct array access you get with a for loop.

另一方面，foreach 则更加省心一些。它为你遍历每个元素，而且写起来更简洁，因为你不需要处理计数器或索引。在底层，foreach 使用一个枚举器（enumerator）对象来跟踪它在数组中的位置。这个枚举器增加了一点额外的开销，因为它在你的代码和通过 for 循环获得的直接数组访问之间多了一层。

Especially with arrays, which are a simple and fast data structure, the extra overhead of foreach can make it a bit slower than a for loop. This doesn't mean much for small arrays or when you're not looping very often, but in performance-critical applications, like graphics rendering or real-time data processing, where every millisecond counts, preferring for loops over foreach can add up to significant performance gains.

特别是对于数组这种简单且快速的数据结构，foreach 的额外开销可能使其比 for 循环稍慢一些。对于小型数组或者你不经常循环的情况，这没有多大区别，但在性能关键型应用中，比如图形渲染或实时数据处理，每一毫秒都很重要，优先使用 for 循环而非 foreach 可以累积成显著的性能提升。

Let's see a simple example comparing the two:

让我们看一个简单的示例来比较两者：

Using a for loop:

使用 for 循环：

var numbers = new int[] { 1, 2, 3, 4, 5 };

for (int i = 0; i < numbers.Length; i++)
{
    Console.WriteLine(numbers[i]);
}

Using a foreach loop:

使用 foreach 循环：

foreach (int number in numbers)
{
    Console.WriteLine(number);
}

In performance tests and studies, such as those you might find in software engineering blogs or performance analysis papers, for loops consistently outperform foreach when iterating over arrays. These tests show that while the difference in a single iteration might be minimal, in high-load scenarios where loops are running millions of times, the time saved by using for loops can be substantial.

在性能测试和研究中，比如你可以在软件工程博客或性能分析论文中找到的那些，for 循环在遍历数组时始终优于 foreach。这些测试表明，虽然单次迭代中的差异可能微乎其微，但在循环运行数百万次的高负载场景中，使用 for 循环节省的时间可能相当可观。

When iterating over arrays in C#, choosing between a for loop and a foreach loop can impact performance. A for loop can be more efficient, especially with arrays, because it works with the index directly, leading to faster access times. In contrast, foreach uses an enumerator which adds overhead. Performance tests have shown that using a for loop can be about 2-3 times faster than using foreach. These findings are consistent across different versions of .NET, including .NET Framework 4.7.2 and .NET Core 3. See documentation.

在 C# 中遍历数组时，选择 for 循环还是 foreach 循环会影响性能。for 循环可以更高效，特别是对于数组，因为它直接使用索引，从而获得更快的访问时间。相比之下，foreach 使用枚举器，这增加了开销。性能测试表明，使用 for 循环的速度大约是使用 foreach 的 2-3 倍。这些发现在不同版本的 .NET（包括 .NET Framework 4.7.2 和 .NET Core 3）中都是一致的。参见文档。

When processing data, especially in performance-critical applications, this efficiency difference is significant. While foreach may be cleaner and easier to write, for loops provide a more performant alternative, particularly when working with large data sets or in tight loops where the overhead of foreach could accumulate. The recommendation is to use for loops in scenarios where performance is a key concern, and to use foreach judiciously, being aware of its potential impact on the application's responsiveness and efficiency. In conclusion, while foreach might offer cleaner syntax and is perfectly fine for most cases, if you're looking to squeeze out every bit of performance, especially in a tight loop over an array, go for a for loop. It's a simple change that can lead to better performance in your code.

在处理数据时，尤其是在性能关键型应用中，这种效率差异是显著的。虽然 foreach 可能更简洁、更容易编写，但 for 循环提供了更高性能的替代方案，特别是在处理大型数据集或在 foreach 的开销可能累积的紧密循环中。建议是在性能是关键关注点的场景中使用 for 循环，并审慎地使用 foreach，要意识到它对应用程序响应能力和效率的潜在影响。总之，虽然 foreach 可能提供更简洁的语法，并且在大多数情况下完全没问题，但如果你想要榨取每一点性能，特别是在对数组的紧密循环中，就选择 for 循环。这是一个简单的改变，可以为你的代码带来更好的性能。

---

Suleyman Cabir Ataman, PhD

---

This entry is part 13 of 17 in the series Advanced C# Tips.
本文是 Advanced C# Tips（高级 C# 技巧） 系列 17 篇中的第 13 篇。