id	author	title	date	pages	extension	mime	words	sentences	flesch	summary	cache	txt
bibwild-wordpress-com-8791		Comparing performance of a Rails app on different Heroku formations – Bibliographic Wilderness			.html	text/html	7537	631	79	This throughput under load can be effected not only by changing base speed, but also by various forms of horizontal scaling — how many puma or passenger processes you have with how many threads each, and how many CPUs they have access to, as well as number of heroku dynos or other hosts behind a load balancer. I decided to leave threads set to 1, and vary connections for load — so -c1 -t1 is a "one URL at a time" setting we can use to test "base speed", and we can benchmark throughput under load by increasing connections. Measuring base speed (just one concurrent request at a time), we found that performance dynos seem to have about the CPU speed of a bursting t2.medium (just a hair slower). But in fact, heroku standard dynos are much slower and more variable in performance than a bursting t2.medium.	./cache/bibwild-wordpress-com-8791.html	./txt/bibwild-wordpress-com-8791.txt