In this talk we will examine various .NET performance tips under the microscope – using various tools we’ll visualize various boxing and hidden memory allocations that occur normally, and learn how to deal with them!

1. .NET Performance Tips
#VISUALIZED
Igal Tabachnik
@hmemcpy

2. WoW – Word of Warning
•10 PREMATURE OPTIMIZATION
' …is the root of all evil (mostly)
•20 MEASURE ALL THE THINGS
' otherwise, you’re guessing
•30 GOTO 10

3. High Memory Traffic
• Garbage Collection (GC) internals are unknown to the public
(yet). Only the CLR team knows what’s really going on.
• Gen0 -> Gen1 -> Gen2
• More memory traffic = more GC time/app freeze/OOM

4. Memory Traffic: GC Pressure
•Hidden allocations
•Boxing
•Other stuff

5. LINQ

7. More LINQ

9. params

10. params – decompiled

11. IEnumerable<T> vs List<T>

12. IEnumerable<T> vs List<T>

13. /j #DEMO

14. GC.Collect()
GOTO 10

15. Finalize()
•Google:
• “resharper heapview”
• “roslyn perf tips” (bit.ly/dotnet-perf)
• “download ozcode” :)

16. THANK YOU!
•/msg nickserv +twitter @hmemcpy
• /msg nickserv +email hmemcpy@gmail.com