Scalability

http://www.codinghorror.com/blog/2009/06/scaling-up-vs-scaling-out-hidden-costs.html blog post about scale up and scale out, and hidden costs introduced by administration licensing costs for proprietary software. “Last monday we upgraded our core database server after a power outage knocked the site offline. I haven’t touched this machine since 2005 so it was a major undertaking to do it last minute. We upgraded from a machine with 64 GB of ram and 8 CPUs to a HP ProLiant DL785 with 512 GB of ram and 32 CPUs …” ...

http://www.codinghorror.com/blog/2009/06/scaling-up-vs-scaling-out-hidden-costs.html blog post about scale up and scale out, and hidden costs introduced by administration licensing costs for proprietary software. “Last monday we upgraded our core database server after a power outage knocked the site offline. I haven’t touched this machine since 2005 so it was a major undertaking to do it last minute. We upgraded from a machine with 64 GB of ram and 8 CPUs to a HP ProLiant DL785 with 512 GB of ram and 32 CPUs …” ...

http://highscalability.com/blog/2013/3/13/ironio-moved-from-ruby-to-go-28-servers-cut-and-colossal-clu.html sometimes language makes a difference ( i.e ruby is too low for a service stack )

http://highscalability.com/blog/2013/3/13/ironio-moved-from-ruby-to-go-28-servers-cut-and-colossal-clu.html sometimes language makes a difference ( i.e ruby is too low for a service stack )

http://labs.linkfluence.net/nosql/2011/03/07/moving_from_couchdb_to_riak.html another article about migration to Riak

http://labs.linkfluence.net/nosql/2011/03/07/moving_from_couchdb_to_riak.html another article about migration to Riak

http://labs.linkfluence.net/nosql/2011/03/07/moving_from_couchdb_to_riak.html another article about migration to Riak

http://haproxy.1wt.eu/10g.html

http://haproxy.1wt.eu/10g.html HA Proxy [synthetic] benchmarks on 10Gbit traffic. Linux network stack is the bottle neck here, not HAProxy, i.e. you can 10G line rate on big frames and few connections.

http://vbtechsupport.com/606/ Sysbench-based benchmark comparing OLTP workloads for different builds and forks of MySQL on 64-core intel machine (Quad Intel Xeon L7555 ) . Only one definitive result is that MySQL cannot scale beyond 8 or 16 cores, or in some cases beyond just 2 cores (booo! ). In all cases performance went down when more than 24 cores were used .