Welcome to Mordor - Daniel Kahn - Codemotion Amsterdam 2016
•Télécharger en tant que PPTX, PDF•
0 j'aime•1,106 vues
If there is bad press about Node.js it's because of performance issues and how hard it is to track them down. Usually these problems are hiding during development but start to kick in under high load. Not good. In my talk we will briefly go through the "hall of fame" of Node.js performance problems and the technical details behind them. By doing so, we will also get some valuable insights on how Node.js (V8, libuv) works internally. Then we will learn how to create metrics that the V8 engine provides to us out of the box and learn about tools that help interpreting them.
Recommandé
Contenu connexe
En vedette
En vedette (20)
Similaire à Welcome to Mordor - Daniel Kahn - Codemotion Amsterdam 2016
Similaire à Welcome to Mordor - Daniel Kahn - Codemotion Amsterdam 2016 (20)
Plus de Codemotion
Plus de Codemotion (20)
Dernier
Dernier (20)
Welcome to Mordor - Daniel Kahn - Codemotion Amsterdam 2016
- 1. Hunting Performance Problems in Node.js CodeMotion Amsterdam 2016 Daniel Khan | @dkhan
- 7. Node.js is what the Company Outlaws use to finally introduce change
- 11. Node.js is what the Company Hipsters threw in just to break everything
- 14. Node.js is a C++ program controlled by V8 JavaScript
- 20. process.memoryUsage() { rss: 4935680, heapTotal: 1826816, heapUsed: 650472 }
- 31. How to build a Memory Leak
- 35. http://bit.ly/1PvijIy var snap = profiler.takeSnapshot(); snap.serialize(); v8-profiler
- 36. D e l t a
- 45. get(‘/routeA’, function(){}) get(‘/routeB’, function(){}) get(‘/routeC’, function(){}) get(‘/routeD’, function(){}) get(‘/routeE’, function(){}) get(‘/routeA’, function(){}) get(‘/routeX’, function(){}) get(‘/^(route|router)/(.+)’, function(){}) HTTP GET /routeX get(‘/routeA’, function(){}) get(‘/routeX’, function(){}) O(n)
- 57. 1980 20001995 2005 2010 2015 Stakeholders
- 61. “No man is an island” or … We need a holistic view.
- 62. Meet Application Performance Monitoring
- 73. Takeaways • Node.js introduces change • Use dedicated tools like N|Solid to monitor Node.js specific metrics like CPU and Memory Usage • Protect your boundaries by actively monitoring incoming and outgoing transactions • Use APM Solutions like Dynatrace or Ruxit to get a holistic view for all transactions passing through all tiers of your stack
Notes de l'éditeur
- And this is how we look like on Sundays.
- When I started my career 15 years ago websites looked like this. Cats already dominated the internet. We hated JavaScript. I can’t believe that now 15 years afterwards I am giving a talk about server side JavaScript in San Francisco.
- But I really like this definition.
- What V8 does: It translates JavaScript into machine code and runs it.
- And every running program is represented by Work done on the CPU Data Stoed im memory And here we already have our two problem classes.
- Let’s review the memory handling of Node.js It’s very common and quite like Java. RSS: Code and Stack where local variables are stored It contains the heap for where objects and closures – let’s say long living resources like objects or closures are stored
- And it’s actually very easy to query the memory usage of a given Node process.
- And this is what you get if you create a graph of a running Node application. As we already see the heapUsed graph looks funny. It somehow is very dynamic and seems to follow a pattern. Something seems to take care that memory is freed. And I have a real live example of how this works.
- The console spits this out
- And now that we have found our problem we can add this. And the weekend is saved.
- My script will look at the memory usage and it constantly grows it will create a snapshot.
- Again v8 profiler. Again a function already there in V8. This will give you this.
- We can also look at some color coded chart that shows different function calls and the length. This pretty much resembles the flame charts we saw before. Some people like it – I don’t.
- What I did is: I fed the json tree to d3 sunburst.
- So this netflix latency problem.
- Speaking about Node.js let’s outline what this talk is about. When ever there’s bad press about Node.js it’s about performance problems. Here are two examples.