actual RAM available
$ free | grep 'buffers/cache' | awk '{ print $4 }'
#!/usr/bin/env ruby | |
# -- 8< -- | |
# Original source: https://gist.github.com/840590 | |
# Author: x@ES (KEIvanov@gmail.com) | |
# | |
# This is draft. | |
# | |
# For load test you can run in therminal | |
# $ perl -e '$|=1;do{$l==$r or print "."; $l=$r}until(($r=time-$^T)>5000)' |
$ free | grep 'buffers/cache' | awk '{ print $4 }'
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
var Article = require('../../../models/article');
Those suck for maintenance and they're ugly.
#!/bin/bash | |
echo "# This file is GENERATED, all changes would be overwritten by ~/bin/build_ssh_config, place config to ~/.ssh/config.d/ instead" > ~/.ssh/config | |
cat ~/.ssh/config.d/* >> ~/.ssh/config |