JavaScript engines such as Google’s V8 (Chrome, Node) are specifically designed for the fast execution of large JavaScript applications. As you develop, if you care about memory usage and performance, you should be aware of some of what’s going on in your user’s browser’s JavaScript engine behind the scenes.
Continue reading Writing Fast, Memory-Efficient JavaScript, great general overview of a Google employee
- Faster HTML and CSS: Layout Engine Internals for Web Developers: by David Baron of Mozilla
- Google I/O 2012 - Breaking the JavaScript Speed Limit with V8
- DOM, HTML5, & CSS3 Performance: A video by Paul Irish
- Nicholas Zakas | High Performance Javascript
- General Information
- Memory
- Tools
- Chrome Developer Tools
- V8
- Optimizing for V8 - very technical series on the V8 engine
- I-want-to-optimize-my-JS-application-on-V8 checklist
- Performance tips for JavaScript in V8
- JavaScript Leak Finder
- Navigation Timing
- Firebug Paint Events
- DOM Manipulation
- Rendering: repaint, reflow/relayout, restyle
- Reflows & Repaints: CSS Performance making your JavaScript slow?
- The new game show: "Will it reflow?"
- When does reflow happen in a DOM environment?
- Speeding up JavaScript: Working with the DOM
- Efficient JavaScript on dev.opera.com
- When Does JavaScript trigger reflows and rendering
- How (not) to trigger a layout in WebKit
- Animation
- Hardware Acceleration
- Browser Internals
- How Browsers Work: Behind the scenes of modern web browsers
- How Browsers Work - Part 1 - Architecture
- Know Your Engines at O’Reilly Velocity 2011
- Video: GDC 2012: From Console to Chrome
- Fast CSS: How Browsers Lay Out Web Pages
- Video: What Browsers Really Think of Your App
- WebKit blog five-part series on rendering
- Video: Alex Russell - Life Of A Button Element
- How a web page loads
- Video: The Fundamentals, Primitives and History of HTML5