Masoud Ghorbani msudgh

Moved to git-repository: https://github.com/denji/awesome-http-benchmark

Tools

Located in alphabetical order (not prefer)

ab – slow and single threaded, written in C
apib – most of the features of ApacheBench (ab), also designed as a more modern replacement, written in C
autocannon – fast HTTP/1.1 benchmarking tool written in Node.js
baloo – Expressive end-to-end HTTP API testing made easy, written in Go (golang)

Turning PostgreSQL into a queue serving 10,000 jobs per second

RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.

On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.

So, many developers have started going straight t

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

	import "bytes"

	func StreamToByte(stream io.Reader) []byte {
	buf := new(bytes.Buffer)
	buf.ReadFrom(stream)
	return buf.Bytes()
	}

	func StreamToString(stream io.Reader) string {
	buf := new(bytes.Buffer)

-# delete local tag '12345'
-git tag -d 12345
-# delete remote tag '12345' (eg, GitHub version too)
-git push origin :refs/tags/12345
-# alternative approach
-git push --delete origin tagName
-git tag -d tagName

	#
	# CORS header support
	#
	# One way to use this is by placing it into a file called "cors_support"
	# under your Nginx configuration directory and placing the following
	# statement inside your location block(s):
	#
	# include cors_support;
	#
	# As of Nginx 1.7.5, add_header supports an "always" parameter which

	-- Remove the history from
	rm -rf .git

	-- recreate the repos from the current content only
	git init
	git add .
	git commit -m "Initial commit"

	-- push to the github remote repos ensuring you overwrite history
	git remote add origin [email protected]:<YOUR ACCOUNT>/<YOUR REPOS>.git