willbmoss

8 ms·

1.
Experiment Infrastructure at Airbnb (nerds.airbnb.com)
10 points by willbmoss 12y ago|0 comments
2.
by willbmoss 14y ago
Turns out escaping json suck, so I decided to lean on Python. v2: https://gist.github.com/wmoss/4774406
3.
Pipe to gist(gist.github.com)
1 points by willbmoss 14y ago|1 comments
4.
by willbmoss 14y ago
At high concurrency, I'd argue you will probably end up being more cpu efficient as well. The cost of context switching effectively larger frames and getting into and out of privileged mode can get expensive.
5.
by willbmoss 14y ago
We had two replica sets of three nodes each. After the first migration, we took it down to one replica set.
6.
by willbmoss 14y ago
I agree with you in theory, in practice, my experience has been a bit different. Specifically, 1. Since Mongo has a database (or maybe collection now) level lock, doing rebalancing under a heavy write load is impossible. 3. Mongos creates o
7.
by willbmoss 14y ago
I'll agree they are not operational nightmares, but now that we're set up with Riak we can do things that I'm pretty sure your Postgres/MySQL/etc. setup cannot. 1. Add individual nodes to the cluster and have it automatically rebalance over
8.
by willbmoss 15y ago
In a nutshell, gevent monkey patches the socket library, whereas diesel doesn't. This means that you can use any (previously) blocking libraries with gevent, whereas, in diesel you have to write them again. The upside of the rewriting is th
9.
by willbmoss 15y ago
I added an implementation [1] in diesel [2][3], which uses select.epoll (or libev, on non-Linux systems) and got a around 150x speedup [4]. I only repeated the tests a few times (but they were all close) and didn't install the Go compiler s
10.
by willbmoss 15y ago
Agreed, I should have clarified. We don't just use IRC, but IRC along with other tools to handle pasting text and file uploads. I think what has always bothered me about Campfire (which I'm sure can be solved) is that it's not easy to do th
11.
by willbmoss 15y ago
At Bump we tried Campfire, but ended up using IRC (and use an open source IRC bot, https://bitbucket.org/yougov/pmxbot/src ). I'm curious why you decided to go with Campfire instead of IRC.
12.
by willbmoss 15y ago
We (Bump) have found two bugs in Redis and both times we've worked closely with Salvatore and had them fixed in less than 48 hours. He's a great programmer who really cares about the product.
13.
by willbmoss 15y ago
One thing you don't note in your post (but made a big difference for us) is that 2.4 uses jemalloc. This reduced memory fragmentation for us by around 25%.
14.
by willbmoss 15y ago
Just as a word of warning, Redis 2.2 cannot read rdb or aof files created by 2.4 (meaning I'm pretty sure 2.2 can't be a slave of 2.4. So, if you have a fail over scenario, you might be forced to upgrade your master to 2.4.
15.
by willbmoss 15y ago
Bitcask can guarantee one disk seek, whereas LevelDB will do one disk seek per level, so at least from that perspective, it can't be better. Level also has to look down the entire tree if a key is missing. This means inserts end up being mo
16.
by willbmoss 15y ago
Mathias, what Riak (or other distributed databases provide) that Mongo doesn't is "just-works" scaling characteristics beyond one machine. * If I want to ensure that my data is written to three machines, all my writes will stop working in M
17.
by willbmoss 15y ago
It's worth noting that not only is the list keys operation expensive, but since it uses Bloom filters, it's not guaranteed to returns all keys. My sources at Basho tell me that this is fixed in 1.0, but until that's officially released, bas
18.
by willbmoss 15y ago
I wrote the post and to clarify, I didn't mean to suggest that interfacing with Android was impossible with Clojure, simply that is was easier with Scala. As rickmode points out, there are some things that make Clojure more difficult.
19.
by willbmoss 17y ago
Is this what you are looking for? http://goloco.org/
20.
by willbmoss 17y ago
Agreed, a very cool idea. I believe you are right on the parallelism front, cloud.call just offloads the processing on their servers, but you'd have to call it multiple times to get any parallelism.