natebrennand | 4 months ago | on: Corrosion
natebrennand's comments
natebrennand | 10 months ago | on: The fastest Postgres inserts
natebrennand | 8 years ago | on: Ask HN: In what creative ways are you using Makefiles?
natebrennand | 10 years ago | on: Clarifications about Redis and Memcached
https://www.usenix.org/system/files/conference/osdi14/osdi14...
natebrennand | 10 years ago | on: Projects the Hard Way – Coding Projects for Early Coders
natebrennand | 11 years ago | on: RethinkDB 2.0 is amazing
https://groups.google.com/forum/#!searchin/rethinkdb/meteor/...
natebrennand | 11 years ago | on: “Go’s design is a disservice to intelligent programmers”
natebrennand | 11 years ago | on: Show HN: Simple wiki server written in Go
http://gophercon.sourcegraph.com/post/83845316771/panel-disc...
natebrennand | 11 years ago | on: Ex-Googlers CockroachDB: A Scalable, Geo-Replicated, Transactional Datastore
[0]: https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLo...
natebrennand | 11 years ago | on: GitHub Student Developer Pack
natebrennand | 11 years ago | on: Neovim Newsletter – Issue #1 – A New Hope
natebrennand | 12 years ago | on: An Introduction to Programming in Go
natebrennand | 12 years ago | on: Speed memory access by arranging data to take advantage of CPU caching
In case you missed it, there was a relevant article last week about how B-Trees benefit by reducing the number of cache requests.
[1]. http://db.lcs.mit.edu/projects/cstore/abadisigmod06.pdf
natebrennand | 12 years ago | on: PostgreSQL Columnar Store for Analytic Workloads
The improvements to your first two points are typically 1-2 magnitudes faster with column-stores [2].
[1] http://db.lcs.mit.edu/projects/cstore/abadisigmod06.pdf
[2] http://db.csail.mit.edu/projects/cstore/abadi-sigmod08.pdf
natebrennand | 12 years ago | on: GitHub's language detection is broken
https://github.com/github/linguist/blob/master/lib/linguist/...
natebrennand | 12 years ago | on: Beat This Level, Get A Programming Job
1. http://bits.blogs.nytimes.com/2011/09/14/codecademy-offers-f...
natebrennand | 12 years ago | on: How to Hire
This tier approach makes a lot of sense to mitigate the scaling limit per corrosion node. Can you share how much data you wind up tracking in each tier in practice?
How concise is the entry for each application -> [regions] table? Does the constraint of running this on every node mean that this creates a global limit for number of applications? It also seems like the region level database would have a regional limit for the number of Fly machines too?