Here is a collection of tips and tricks I've picked up about doing performance analysis on Node. Included is a build script that should get a base install of Ubuntu fully functional and ready for all the things we'll be going through.
The script pulls a lot of code from the latest master of each repository. So
it's possible that something may fail, but to date I haven't had any issues.
First, go ahead and run the script. Then go take a nice long break. It'll
The prep-script.sh will setup the latest Node and install the latest perf version on your Linux box.
When you want to generate the flame graph, run the following (folder locations taken from install script):
sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0
| [{"index": 0, "id": "<redacted>", "habit": {"week": "2013-08-26", "goal_units": "timedelta", "daily_scores": [{"total_points": 128, "state": 13, "score": 1439, "goal": 720.0, "last_timestamp": "2013-08-26T23:59:00+5:00", "base_points": 25, "day": "monday"}, {"total_points": 125, "state": 13, "score": 1438, "goal": 720.0, "last_timestamp": "2013-08-27T23:59:00+5:00", "base_points": 25, "day": "tuesday"}, {"total_points": 125, "state": 13, "score": 1439, "goal": 720.0, "last_timestamp": "2013-08-28T23:59:00+5:00", "base_points": 25, "day": "wednesday"}, {"total_points": 125, "state": 13, "score": 1430, "goal": 720.0, "last_timestamp": "2013-08-29T23:59:00+5:00", "base_points": 25, "day": "thursday"}, {"total_points": 125, "state": 13, "score": 1440, "goal": 720.0, "last_timestamp": "2013-08-30T23:59:00+5:00", "base_points": 25, "day": "friday"}, {"total_points": 125, "state": 13, "score": 1434, "goal": 720.0, "last_timestamp": "2013-08-31T23:59:00+5:00", "base_points": 25, "day": "saturday"}, {"total_points": 1 |
| // http://worlds.simcity.com/parallelworlds.json | |
| // | |
| // Intercepting this request and changing the "Desc" field does nothing to the | |
| // game's UI. The name in the interface seems to come from looking up the "id" | |
| // field against a list of names stored internally. Probably because of locale | |
| // stuff. | |
| // | |
| // Note the hidden servers! | |
| { |
| function! EditScss() | |
| " The current file | |
| let file = expand("%") | |
| " The current file's basename plus .scss | |
| let scss = expand("%:r") . ".scss" | |
| " If the file exists | |
| if filereadable(scss) | |
| " Prompt the user and store the user's choice (1-indexed) in a variable |
| license: gpl-3.0 |
| license: gpl-3.0 |
