Hunting Performance Problems in Node.js and beyond
-
Upload
daniel-khan -
Category
Internet
-
view
307 -
download
0
Transcript of Hunting Performance Problems in Node.js and beyond
NODE_ENV=productionNODE_ENV=development
Blog: http://bit.ly/1flz0Xm
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)
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