Performance In The .Net World
- 1. Performance in the .NET world. A developer’s perspectiveSorin Oboroceanu, Vlad BalanRomSoft, www.rms.roIaşi, May 4th 2010
- 2. AgendaString vs. StringBuilderSerializationReading XMLGarbage CollectionJITing2
- 4. Our Demo APPUses StackOverflow.com’s dataGroups users by locationDisplays user locations in a chartWill work in a client/server architectureHas performance issues 4
- 5. CollectionsGroupping dataList<T>LINQ to ObjectsDictionary<T,V>5DEMO
- 6. Client-Server communicationRetrieving all users on the clientGrouping dataList<T>LINQ to ObjectsDictionary<T,V>6DEMO
- 7. Client-Server communicationGrouping data on the serverList<T>LINQ to ObjectsDictionary<T,V>Retrieving only location-related data on the client7DEMO
- 8. Reading XMLDataSetXmlReaderLINQ to XMLXmlDocument8DEMO
- 9. Garbage CollectionWhy memory mattersGarbage CollectorCommon Memory IssuesDiagnosing Memory Problems 9
- 10. Why memory mattersInefficient use of memory can impactPerformanceStabilityScalabilityOther ApplicationsHidden problems in code can causeMemory LeaksExcessive memory usageUnnecessary performance overhead10
- 11. GC – Small Object Heap (SOH)11GCSmallObjectObjectA = new SmallObject(); SmallObjectObjectB = new SmallObject(); Global ObjectsSmall Object HeapNext Object PointerObjectENext Object PointerStackObjectDStatic ObjectsNext Object PointerObjectCNext Object PointerObjectBObjectBNext Object PointerObjectAObjectARoot ReferenceNext Object PointerChild Reference
- 12. GC- Gen2LargeObjectObjectD= new LargeObject(); Global ObjectsFree space tableLarge Object Heap42500016777216ObjectD572740094208182272Free spaceStackObjectCObjectCObjectBFree spaceObjectBObjectAObjectA1212
- 13. 13GC - Gen 0GC - Gen 1GC - Gen 2Small Object HeapGen 0Next Object PointerGlobal ObjectsObjectDObjectCNext Object PointerGen 1Static ObjectsStackObjectBGen 2ObjectARoot Reference
- 14. GC – Minimizing Overheadpublic class Test: IDisposable{ ~Test() { Cleanup (false); } private void Cleanup(boolcodeDispose) { if (codeDispose) { // dispose managed resources } // clean up unmanaged resources } public void Dispose() { Cleanup (true); GC.SuppressFinalize(this); } }14
- 15. GC – Common Memory IssuesExcessive RAM FootprintApp allocates objects too early or for too long using more memory than neededCan affect other apps on the systemExcessive Temporary Object allocationGarbage Collection runs more frequentlyExecuting threads freeze during Garbage CollectionMemory LeaksOverlooked root references keep objects alive (Collections, array, session state, delegates/events)Incorrect or absent Finalization can cause resources leaks15
- 16. DEMO16
- 17. JITing17Consolestatic void WriteLine();static void WriteLine(string);(remaining members)Managed EXEstatic void Main(){Console.WriteLine(“Hello”);Console.WriteLine(“GoodBye”);}JITCompilerJITCompilerMSCorEE.dll…JITCompiler function{Look up the called method in the metadataGet the IL for it from metadataAllocate memoryCompile the IL into allocated memoryModify the method’s entry in the Type’s table so it points to allocated memoryJump to the native code contained inside the memory block.}Native CPU instr.
- 18. JITing18Consolestatic void WriteLine();static void WriteLine(string);(remaining members)Managed EXEstatic void Main(){Console.WriteLine(“Hello”);Console.WriteLine(“GoodBye”);}JITCompilerNativeMSCorEE.dll…JITCompiler function{Lookup the called method in the metadataGet the IL for it from metadataAllocate memoryCompile the IL into allocated memoryModify the method’s entry in the Type’s table so it points to allocated memoryJump to the native code contained inside the memory block.}Native CPU instr.
- 19. DEMO19
- 20. ResourcesCLR via C# 3, Jeffrey Richterwww.red-gate.comwww.stackoverflow.comMSDN20
- 21. Q&A21
- 22. 22Please fill the evaluation formThank you very much!Sorin Oboroceanu, Vlad BalanRomSoft, www.rms.roIasi, May 4th 2010