Viewing profile — willbmoss
willbmoss
HN member- Joined
- Tue, Dec 22, 2009, 7:43 PM UTC
- HN karma
- 48
- Public activity
- 20 items
- HN profile
- View on Hacker News ↗
About willbmoss
No profile information was provided.
Recent public activity
- story
-
comment
Comment #5210235
Turns out escaping json suck, so I decided to lean on Python. v2: https://gist.github.com/wmoss/4774406
- story
-
comment
Comment #4033151
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 privil…
-
comment
Comment #3974827
We had two replica sets of three nodes each. After the first migration, we took it down to one replica set.
-
comment
Comment #3974659
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…
-
comment
Comment #3973805
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 n…
-
comment
Comment #3735137
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…
-
comment
Comment #3733265
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 (b…
-
comment
Comment #3155956
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 (…
-
comment
Comment #3155618
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 instea…
-
comment
Comment #3112901
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 t…
-
comment
Comment #3112896
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%.
-
comment
Comment #3112886
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 mig…
-
comment
Comment #3045421
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 …
-
comment
Comment #2971407
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 wri…
-
comment
Comment #2971332
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 thi…
-
comment
Comment #2651207
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, t…
-
comment
Comment #1167408
Is this what you are looking for? http://goloco.org/
-
comment
Comment #1155814
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 ge…