https://github.com/chariotsolutions/node-behaving--badly
Pay no attention to the man behind the curtain. It's just Ken Rimple trying to make Node behave rather badly... Any crazy ideas are his own.
https://github.com/chariotsolutions/node-behaving--badly
Last synced: 5 months ago
JSON representation
Pay no attention to the man behind the curtain. It's just Ken Rimple trying to make Node behave rather badly... Any crazy ideas are his own.
- Host: GitHub
- URL: https://github.com/chariotsolutions/node-behaving--badly
- Owner: chariotsolutions
- Created: 2016-06-20T19:03:09.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2016-07-14T21:57:35.000Z (about 10 years ago)
- Last Synced: 2025-01-08T13:41:21.419Z (over 1 year ago)
- Language: HTML
- Homepage: http://chariotsolutions.com/blog/post/introducing-nsolid-node-js-application-profiler/
- Size: 671 KB
- Stars: 5
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# node-behaving--badly
This is why we can't have nice things. You shouldn't do the following things directly in Node user-land JavaScript (i.e. the Event Loop) without understanding why:
* Template processing
* Heavy-duty collections processing
* High-cpu work
This repo is a sandbox for writing terribly performing code in Node.js so you can observe it and see how problems might occur in the field. Some of the ideas here:
* Using functional methods from tools like ramda and async to process large amounts of data
* Wasting memory in terrible ways
* Causing everybody to think your code is dead by starving the event loop
Now I assume your code won't behave like this! Use N|Solid or other tools to profile it and slay those terribly performing dragons.
Enjoy?
Ken Rimple
July 2016