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

Stop Crying and Start Profiling #75

Open
xjamundx opened this issue Jan 11, 2014 · 0 comments
Open

Stop Crying and Start Profiling #75

xjamundx opened this issue Jan 11, 2014 · 0 comments

Comments

@xjamundx
Copy link

At some point you realize that node isn't always fast and you have a little cry, but then you move on and try to fix the problem.


Profiing is how you figure out what's going on.


We recently had an issue with some NPM modules slowing down our node experience. Breakpoints and console.log weren't really getting us any closer to solving the problem. Eventually we figured out how to profile the app and look at what was actually happening inside.

debug

This allowed to track down the problem and come up with some patches to keep things running speedily.


Probably everyone will have that problem at some point, so talking about these tools should be helpful for a wide audience! And 20 minutes is perfect.


I'd like to cover the tools that I've used to solve real problems:

I'd be happy to discuss other things if there are better tools out there for the masses.

🚗 - 🚴 - 🏊 - 🚗 - 🚴 - 🏊 - 🚗 - 🚴 - 🏊 - 🚗 - 🚴 - 🏊 - 🚗 - 🚴 - 🏊 - 🚗

p.s. No SmartOS Required

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