Look Beyond console.log

Dominic Umbeer will share some approaches to keep track of system performance and tools for debugging and performance analysis, such as node-inspect, node-prof, and Chrome DevTool.

Transcript

1. b Node.js Meetup #29
2. b Node.js Meetup #9
3. b Look Beyond console.log January 2018
4. b Dominic Umbeer Software Engineer, CTO @ blogfoster Blog: http://engineering.blogfoster.com Twitter: @dominicumbeer
5. b Debugging
6. b console.log()
7. b Dominic's Debugging Workflow Recognized Problem Open Editor Open File Add Debugging Code Switch to Terminal Simulate Error Case Analyze Terminal Output Fix Problem
8. b Dominic's Debugging Workflow Recognized Problem Open Editor Open File Add Debugging Code Switch to Terminal Simulate Error Case Analyze Terminal Output Fix Problem
9. b Basics - Inspector https://nodejs.org/en/docs/inspector/
10. b Basics - Inspector
11. b Basics - ChromeDevTools chrome://inspect
12. b Basics - ChromeDevTools
13. b Basics - ChromeDevTools
14. b Demo: Just Do It!
15. b Improved Debugging Workflow Recognized Problem Open Editor Open File Add Debugging Code Switch to Terminal Simulate Error Case Analyze Terminal Output Fix Problem
16. b Performance
17. b 80 / 20 Rule 80 percent of your outcomes come from 20 percent of your inputs
18. b Performance KPIs • Event Loop • CPU Utilization • Memory • HTTP: Response Time
19. b Tools 1. V8 profiler - tick profiler 2. ChromeDevTools - JS CPU Profiler
20. b Demo: Just Do It!
21. b Tick Profiler Report
22. b Still Name Your Callbacks
23. b Demo: Just Do It!
24. b Conclusion 1. Tools are your friends -> use it! 2. Look beyond console.log
25. b Thank You All about Javascript: http://engineering.blogfoster.com