No matter how well-built your applications are, countless issues can cause performance problems, putting the platforms they are running on under scrutiny. If you’ve moved to Node.js to power your applications, you may be at risk of these issues calling your choice into question. How do you identify vulnerabilities and mitigate risk to take the focus off troubleshooting the technology and back where it belongs, on innovation?

1. Hunting Performance Problems in Node.js
Daniel Khan | @dkhan

2. @dkhan

3. @dkhan

4. @dkhan

5. @dkhan

6. @dkhan

7. Node.js is
what the Company Outlaws
use to finally introduce change
@dkhan

8. @dkhan

9. @dkhan

11. Node.js is
what the Company Hipsters threw in
just to break everything
@dkhan

12. @dkhan

13. Proactive Defense
@dkhan

14. Node.js is a C++ program controlled by V8
JavaScript
@dkhan

15. @dkhan

16. @dkhan

17. @dkhan

18. Hunting Memory
Problems
@dkhan

19. @dkhan

20. process.memoryUsage()
{ rss: 4935680, heapTotal: 1826816, heapUsed: 650472 }
@dkhan

21. @dkhan

25. @dkhan

26. @dkhan

27. @dkhan

28. @dkhan

29. @dkhan

30. @dkhan

31. How to build
a Memory Leak

32. @dkhan

33. theThing
someMethod()
longStr
unused()
originalThing
Closure Context
Reference
Root
@dkhan

35. @dkhan

36. http://bit.ly/1PvijIy
var snap = profiler.takeSnapshot();
snap.serialize();
v8-profiler
@dkhan

37. D
e
l
t
a
@dkhan

38. Hunting CPU
Problems
@dkhan

39. calculateFibonacci();
@dkhan

40. http://bit.ly/1jQMbBR
profiler.startProfiling(id);
profiler.stopProfiling(id);
v8-profiler
@dkhan

42. @dkhan

43. @dkhan

44. NODE_ENV=productionNODE_ENV=development
Blog: http://bit.ly/1flz0Xm
@dkhan

45. @dkhan

46. 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)
@dkhan

47. Finding the route
@dkhan

48. @dkhan

50. @dkhan

51. @dkhan

52. @dkhan

53. @dkhan

54. @dkhan

55. @dkhan

56. @dkhan

58. 1980 20001995 2005 2010 2015
Stakeholders
@dkhan

60. 1000 RPS
Node.js
10 RPS
Ancient Legacy Backend

61. @dkhan

62. @dkhan

63. @dkhan

64. “No man is an island”
or … We need a holistic view.

65. Meet Application Performance Monitoring
@dkhan

66. @dkhan

68. @dkhan

69. @dkhan

72. @dkhan

73. @dkhan

74. Don’t be the one to
blame!
@dkhan

75. #1 Monitor Memory Consumption
@dkhan

76. #2 Monitor CPU Usage
@dkhan

77. #3 Protect your Boundaries

79. @dkhan
Daniel Khan
daniel.khan@dynatrace.com
Node.js Technology Lead