Why is this faster on 64 bit than 32 bit?

by

x64 processors contain 64 bit general purpose registers with which they can calculate operations on 64 bit integers in a single instruction. 32 bit processors does not have that. This is especially relevant to your program as it’s heavily using long (64-bit integer) variables.

For instance, in x64 assembly, to add a couple 64 bit integers stored in registers, you can simply do:

; adds rbx to rax
add rax, rbx

To do the same operation on a 32 bit x86 processor, you’ll have to use two registers and manually use the carry of the first operation in the second operation:

; adds ecx:ebx to edx:eax
add eax, ebx
adc edx, ecx

More instructions and less registers mean more clock cycles, memory fetches, … which will ultimately result in reduced performance. The difference is very notable in number crunching applications.

For .NET applications, it seems that the 64-bit JIT compiler performs more aggressive optimizations improving overall performance.

Regarding your point about array iteration, the C# compiler is clever enough to recognize foreach over arrays and treat them specially. The generated code is identical to using a for loop and it’s in recommended that you use foreach if you don’t need to change the array element in the loop. Besides that, the runtime recognizes the pattern for (int i = 0; i < a.Length; ++i) and omits the bound checks for array accesses inside the loop. This will not happen in the LongLength case and will result in decreased performance (both for 32 bit and 64 bit case); and since you’ll be using long variables with LongLength, the 32 bit performance will get degraded even more.

More Related Contents:

  1. Performance loss caused by Linq [duplicate]
  2. Is DateTime.Now the best way to measure a function’s performance? [closed]
  3. Is “else if” faster than “switch() case”? [duplicate]
  4. How does having a dynamic variable affect performance?
  5. How costly is .NET reflection?
  6. Performance differences between debug and release builds
  7. Performance surprise with “as” and nullable types
  8. C# Sort and OrderBy comparison
  9. Stopwatch vs. using System.DateTime.Now for timing events [duplicate]
  10. If vs. Switch Speed
  11. SQL Query slow in .NET application but instantaneous in SQL Server Management Studio
  12. LINQ Ring: Any() vs Contains() for Huge Collections
  13. Exact time measurement for performance testing [duplicate]
  14. String concatenation vs String Builder. Performance
  15. Float vs Double Performance
  16. Any way to SQLBulkCopy “insert or update if exists”?
  17. Efficient way to delete a line from a text file
  18. How to write super-fast file-streaming code in C#?
  19. Performance of “direct” virtual call vs. interface call in C#
  20. How accurate is System.Diagnostics.Stopwatch?
  21. DateTime.DayOfWeek micro optimization
  22. Ternary operator is twice as slow as an if-else block?
  23. Entity Framework initialization is SLOW — what can I do to bootstrap it faster?
  24. HTTPWebResponse + StreamReader Very Slow
  25. XmlSerializer Performance Issue when Specifying XmlRootAttribute
  26. Array bounds check efficiency in .net 4 and above
  27. Thread.Sleep(0) : What is the normal behavior?
  28. Performance of Skip (and similar functions, like Take)
  29. Is BitArray faster in C# for getting a bit value than a simple conjuction with bitwise shift?
  30. Fastest way to remove first char in a String

Leave a Comment