为什么 Enumerable.Range 比直接的 Yield 循环更快?
下面的代码检查执行相同解决方案的三种不同方法的性能。
public static void Main(string[] args)
{
// for loop
{
Stopwatch sw = Stopwatch.StartNew();
int accumulator = 0;
for (int i = 1; i <= 100000000; ++i)
{
accumulator += i;
}
sw.Stop();
Console.WriteLine("time = {0}; result = {1}", sw.ElapsedMilliseconds, accumulator);
}
//Enumerable.Range
{
Stopwatch sw = Stopwatch.StartNew();
var ret = Enumerable.Range(1, 100000000).Aggregate(0, (accumulator, n) => accumulator + n);
sw.Stop();
Console.WriteLine("time = {0}; result = {1}", sw.ElapsedMilliseconds, ret);
}
//self-made IEnumerable<int>
{
Stopwatch sw = Stopwatch.StartNew();
var ret = GetIntRange(1, 100000000).Aggregate(0, (accumulator, n) => accumulator + n);
sw.Stop();
Console.WriteLine("time = {0}; result = {1}", sw.ElapsedMilliseconds, ret);
}
}
private static IEnumerable<int> GetIntRange(int start, int count)
{
int end = start + count;
for (int i = start; i < end; ++i)
{
yield return i;
}
}
}
结果是:
time = 306; result = 987459712
time = 1301; result = 987459712
time = 2860; result = 987459712
“for 循环”比其他两个解决方案更快并不奇怪,因为 Enumerable.Aggregate 需要更多的方法调用。 然而,真正让我惊讶的是“Enumerable.Range”比“自制的IEnumerable”更快。 我认为 Enumerable.Range 会比简单的 GetIntRange 方法有更多的开销。
造成这种情况的可能原因有哪些?
The code below is checking performance of three different ways to do same solution.
public static void Main(string[] args)
{
// for loop
{
Stopwatch sw = Stopwatch.StartNew();
int accumulator = 0;
for (int i = 1; i <= 100000000; ++i)
{
accumulator += i;
}
sw.Stop();
Console.WriteLine("time = {0}; result = {1}", sw.ElapsedMilliseconds, accumulator);
}
//Enumerable.Range
{
Stopwatch sw = Stopwatch.StartNew();
var ret = Enumerable.Range(1, 100000000).Aggregate(0, (accumulator, n) => accumulator + n);
sw.Stop();
Console.WriteLine("time = {0}; result = {1}", sw.ElapsedMilliseconds, ret);
}
//self-made IEnumerable<int>
{
Stopwatch sw = Stopwatch.StartNew();
var ret = GetIntRange(1, 100000000).Aggregate(0, (accumulator, n) => accumulator + n);
sw.Stop();
Console.WriteLine("time = {0}; result = {1}", sw.ElapsedMilliseconds, ret);
}
}
private static IEnumerable<int> GetIntRange(int start, int count)
{
int end = start + count;
for (int i = start; i < end; ++i)
{
yield return i;
}
}
}
The results are:
time = 306; result = 987459712
time = 1301; result = 987459712
time = 2860; result = 987459712
It is not surprising that the "for loop" is faster than the other two solutions, because Enumerable.Aggregate takes more method invocations. However, it really surprises me that "Enumerable.Range" is faster than the "self-made IEnumerable". I thought that Enumerable.Range would have more overhead than the simple GetIntRange method.
What are the possible reasons for this?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
为什么
Enumerable.Range
比您自制的GetIntRange
慢? 事实上,如果Enumerable.Range
被定义为那么它应该与您自制的
GetIntRange
一样快。 这实际上是Enumerable.Range
的参考实现,编译器或程序员没有任何技巧。您可能希望将
GetIntRange
和System.Linq.Enumerable.Range
与以下实现进行比较(当然,正如 Rob 指出的那样,在发布模式下编译)。 对于编译器从迭代器块生成的内容,此实现可能会稍微优化。Why should
Enumerable.Range
be any slower than your self-madeGetIntRange
? In fact, ifEnumerable.Range
were defined asthen it should be exactly as fast as your self-made
GetIntRange
. This is in fact the reference implementation forEnumerable.Range
, absent any tricks on the part of the compiler or programmer.You may want to compare your
GetIntRange
andSystem.Linq.Enumerable.Range
with the following implementation (of course, compile in release mode, as Rob points out). This implementation may be slightly optimized with respect to what a compiler would generate from an iterator block.我的猜测是您正在调试器中运行。 这是我的结果,从命令行使用“/o+/debug-”构建,
仍然有轻微的差异,但没有那么明显。 迭代器块实现的效率不如定制的解决方案,但它们非常好。
My guess is that you're running in a debugger. Here are my results, having built from the command line with "/o+ /debug-"
There's still a slight difference, but it's not as pronounced. Iterator block implementations aren't quite as efficient as a tailor-made solution, but they're pretty good.
假设这是正在运行的发布版本,否则所有比较都会关闭,因为 JIT 将无法正常工作。
您可以使用 reflector 查看装配体,看看“yield”声明是什么也在扩大。 编译器将创建一个类来封装迭代器。 也许生成的代码中进行的内务处理比可能是手工编码的 Enumerable.Range 的实现要多
Assuming this is a release build running, otherwise all comparisons are off as the JIT will not be working flat out.
You could look at the assembly with reflector and see what the 'yield' statement is being expanded too. The compiler will be creating a class to encapsulate the iterator. Maybe there is more housekeeping going on in the generated code than the implementation of Enumerable.Range which is likely hand-coded
反射器输出略有不同(以及参数检查和额外的内化水平,这里绝对不相关)。 基本代码更像是:
也就是说,它们不是另一个局部变量,而是为每个收益应用一个额外的加法。
我尝试对此进行基准测试,但我无法停止足够的外部进程来获得可理解的结果。 我还尝试了每个测试两次,以忽略 JIT 编译器的影响,但即使这样也有“有趣”的结果。
这是我的结果示例:
代码
以及编译的
A slight difference in the Reflector output (as well as the argument check and extra level of internalisation definitely not relevant here). The essential code is more like:
That is, instead of another local variable, they apply an extra addition for every yield.
I have tried to benchmark this, but I can't stop enough external processes to get understandable results. I also tried each test twice to ignore the effects of the JIT compiler, but even that has 'interesting' results.
Here's a sample of my results:
and the code
compiled with