spimmy

7 ms·

61.
by spimmy 11y ago
We have a lot of edge cases in our data set and usage model, no question. Glad it's working well for you. :)
62.
by spimmy 11y ago
There's no article, sorry, I just happen to know them.
63.
by spimmy 11y ago
Amen brother. You should never base your db decisions on either marketing copy _or_ HN know-it-all complainypants. :) We actually evaluated TokuMX extensively last year, pre pluggable storage engine. We might have pursued it if they had
64.
by spimmy 11y ago
tszming -- will take care of it, thank you!
65.
by spimmy 11y ago
ah but those particular compression / write rate stats are compared to mmapv1, yeah
66.
by spimmy 11y ago
We're testing with both. Somewhat hindered by the fact that WT often dies trying to import our data, or crashes, or loses data in weird ways. :( I believe WT will eventually get there, but rocks has been unfathomably more solid for
67.
by spimmy 11y ago
Like I said in the post, we're preparing a series of blog posts for next week that does a deep dive into our workloads, our benchmarks, how to repro, etc. Spoiler alert: we consistently get around 90% compression and the inserts are
68.
by spimmy 11y ago
Which data loss issues? You're gonna have to be more specific. ;) It doesn't fix the election rollback issue, because that's handled way above the storage layer. It does solve a whole slew of storage engine related write i
69.
by spimmy 11y ago
God yeah, the write locks have been a pain in my ass for so long. Fortunately the storage engine API delegates locking to the engine, so we get document level locking in RocksDB or WT.
70.
by spimmy 11y ago
Yes and no. (That's my blog post btw.) Mongo is a young database, with some super obvious flaws and growing pains. Some of its bad rep is self-inflicted, when Mongo reps make massively overinflated claims about its reliability, scal
71.
by spimmy 13y ago
What do you mean by "open"? Can the data be used for startups and other commercial purposes?
72.
by spimmy 14y ago
Hm, well Sidekiq wasn't out when we started developing. :) Memory has never been a constraint for us with resque though. The only problems we've had with it have been things like improper signal handling, pretty easy to deal with.
73.
by spimmy 14y ago
We use nginx for serving static files and doing some trivial top-level routing. Haproxy is for load-balancing among families of unicorn app servers.
74.
by spimmy 14y ago
We use redis because we use resque extensively for the push notifications architecture. Memcache is superior to redis for simple caching in front of data sources.