Writing high performance NetCore 3.0 code
•Transferir como PPTX, PDF•
1 gostou•364 visualizações
This document discusses techniques for writing high performance .NET Core 3.0 code. It covers new features like Span<T>, ValueTuple, and C# 8 async streams. It emphasizes that micro-optimizations are only needed for BCL, real-time apps, and graphics. Bottlenecks follow the Pareto principle. The document then discusses specific optimizations for a KTX file loader, including using stackalloc and unsafe code for pinned memory as well as custom collections and multithreading for OpenGL. It concludes by covering new MathF APIs, hardware intrinsics, and taking questions.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Writing high performance NetCore 3.0 code
Semelhante a Writing high performance NetCore 3.0 code (20)
Mais de Plain Concepts
Mais de Plain Concepts (20)
Último
Último (20)
Writing high performance NetCore 3.0 code
- 1. Writing high performance code in NetCore 3.0
- 3. @jcant0n Javier is a Computer Science Engineer who has always had a passion for 3D graphics and software architecture. His professional achievements include being MVP for Windows DirectX and DirectX XNA for the last nine years, Xbox Ambassador, as well as Microsoft Student Partner and Microsoft Most Valuable Student during his years at college. Currently he works at Plainconcepts as Research Team Lead. Javier Cantón Research Team Lead
- 8. .NetCore 3.0 preview Span<T> Memory<T> ValueTuple NetStandard 2.1 C# 8 Async Streams Ref return
- 9. Micro-optimization are for • BCL and Runtime • Real Time applications • Graphics development
- 10. 1 billion operations per day
- 11. 1.000.000.000 / 24 hours 416.666.666 operations per hour
- 12. 416.666.666 / 60 minutes 6.944.444 operations per minutes
- 13. 6.944.444 / 60 seconds 115.740 operations per seconds
- 14. 115.740 / 10 servers 11.5 ms per operation
- 15. Bottlenecks Rule Pareto 20% of the code consume 80% of the resources Pareto^2 4.0% of the code consume 64% of the resources Pareto^3 0.8% of the code consume 51% of the resources
- 16. Real problem
- 17. KTX file loader
- 18. Header
- 19. First attempt
- 20. First attempt
- 21. First attempt
- 22. First attempt
- 23. Issues • GC, Garbage collector • Pinned array
- 24. Value Type vs Reference Type Stack Heap Reference Type Memory Location Int var = 10 Value Type Int var = 10
- 25. And our headerBytes? Stack Heap Reference Type Memory Location 10 72 12
- 26. And our headerBytes? Stack Heap HeaderBytes 10 72 12
- 27. Issues • GC, Garbage collector • Pinned array
- 28. Using stack memory • Stackalloc
- 29. Using stack memory • Unsafe Nuget Library “Provide a generic API to read from and write to a pointer”
- 30. Unsafe class
- 31. Unsafe class
- 33. Real problem
- 36. OpenGL issue • Queue<T> • Interface and struct
- 37. Gen0 Gen1 .NET Managed Heap Gen2 LOH LOH = GEN 2 = FULL GC Size >= 85.000 bytes
- 43. MathF New API for single-precisión math
- 44. MathF 0.00% 10.00% 20.00% 30.00% 40.00% 50.00% 60.00% Pow Exp Tan Atan Atan2 Log Asin Log10 Sinh Cosh Sin Ceiling Acos Floor Cos Sqrt
- 47. Hardware Intrinsics • System.Runtime.Intrinsics • Vector64<T> • Vector128<T> • Vector256<T> • System.Runtime.Intrinsics.X86 • Sse, Sse2,… Sse42 • Avx, Avx2 • Fma • System.Runtime.Intrinsics.Arm.Arm64 • Simd
- 50. Thanks and … See you soon! Thanks also to the sponsors. Without whom this would not have been posible.
Notas do Editor
- No que haya un pico sino mantener este ritmo de operaciones en el tiempo.
- 4.5 x faster.
- Contains generic, low-level functionality for manipulating pointers.
- Contains generic, low-level functionality for manipulating pointers.
- Contains generic, low-level functionality for manipulating pointers.