You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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.
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
The text was updated successfully, but these errors were encountered: