Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Welcome to Mordor! Hunting Performance Issues and Memory Leaks in Node.js #76

Open
danielkhan opened this issue Jul 3, 2015 · 0 comments

Comments

@danielkhan
Copy link

Abstract
If there is bad press about our favourite server side platform it is 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 error patterns behind them.
Then we will take a pleasant walk to "Mount Doom" to understand what flame charts and sunbursts can tell us about our Node.js applications and how to create them yourself.
By doing so, we will even look at some C++ code and - most important - gain some insights on how Node.js works internally.

Bio
Daniel has over 15 years experience as full stack developer, architect and technical lead in the field of web engineering proving his strong problem solving skills in hundreds of projects. He is passionate about constant learning, using new technologies and sharing his findings with others. As technology strategist, Daniel focuses on researching and driving support for emerging technologies like Node.js and MongoDB at Dynatrace - an APM company.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant