Skip to content
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.
HTML JavaScript Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
artillery-scripts
bad-scripts
graphdata
graphs
logs
public
settings
.gitignore
README.md
benchmarks.sh
index.html
launchlocust.sh
locustfile.py
locustfile.pyc
mixed.sh
nsolid-dev-node.sh
nsolid-four-nodes.sh
nsolid-single-node.sh
package.json
server.js

README.md

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

You can’t perform that action at this time.