Performance Engineering using Visual Studio in the era of Cloud Computing
•Als PPTX, PDF herunterladen•
0 gefällt mir•56 views
Slides from my talk for Ottawa .NET Community
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Performance Engineering using Visual Studio in the era of Cloud Computing
Ähnlich wie Performance Engineering using Visual Studio in the era of Cloud Computing (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Performance Engineering using Visual Studio in the era of Cloud Computing
- 1. Performance Engineering with Visual Studio in the era of Cloud Computing Kamran Bilgrami Principal Developer @ Avast (f.k.a AVG)
- 2. What Performance Engineering mean for you?
- 4. Measuring Cost of the Code
- 5. “To be successful at this, you’ll need to know what things cost. If you don’t know what things cost, you’re just flailing in the dark, hoping to get lucky” The 'premature optimization is evil' myth https://goo.gl/U6qpfy
- 6. Software Evolution All in one Client/Server N-Tier Architecture APIs Single Computer Private Data centers Cloud
- 7. Cloud Impact • Lower Cost of Ownership • Level of abstractions • IaaS • PaaS • SaaS
- 8. Cloud Application – Fault Lines • Deployment Model • Single Tenant • Multi Tenant • Hybrid • Fault Lines • Noisy Neighbors • Cascading Affects
- 9. Devs have higher accountability for code cost
- 10. How do you measure cost of your code?
- 11. Tools of the Trade Windbg DebugDiag PerfView Visual Studio
Hinweis der Redaktion
- Performance Engineering means many different thing to different people. What it means for you?
- Key aspect of performance engineering is about measurement. Set goal, track progress by measuring metrics of interest. Depending upon one’s background, everyone may have different favorite metrics to measure (availability, reliability…), - As developers we should have interest in measuring the cost of code we write… Primary focus of talk today
- Code metrics include things like how long it took to run the code, how much memory it consumed, how much cpu cycles it chewed, other resource consumption (network bandwidth, I/O cost etc)
- This is about creating a Performance culture http://joeduffyblog.com/2016/04/10/performance-culture/
- Establish understanding of developer’s role with software evolution over decades
- - Meaning developer’s need to know what their code cost. -With cloud, its just that the scale can change massively which makes cost even more prominent.
- What tools/techniques you have used or can think of could be used to measure cost of your code???
- There are few good commercial tools available but I would talk about few free ones from Microsoft. The idea is to show how much things have changed with Visual Studio
- Windbg ( gc heap, cpu time analysis) DebugDiag (collector/analyzer) PerfView (managed heap/ETW for cpu analysis) Visual Sudio( dump file for memory analysis/diagnostics windows)