@tqbf As for transient storage, misuse runs rampant. Redis should _require_ an "expires" with every call.
-
-
Replying to @KirinDave
@KirinDave There are keyspaces with predictable storage demands and unpredictable expiries. “Transient” maybe imprecise on my part.1 reply 0 retweets 1 like -
Replying to @KirinDave
@KirinDave If growth is predictable and you plan in advance to partition the keyspace, pretty easy to fix that problem.2 replies 0 retweets 0 likes -
Replying to @tqbf
@tqbf@KirinDave if you find yourself wanting to partition the keyspace I really have to ask why you're not using Riak or Cassandra2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@KirinDave How do I efficiently do a set, or do a blocking remove from a list, in Riak?4 replies 0 retweets 0 likes -
Replying to @KirinDave
@KirinDave@bascule Nah, I’m just responding to Tony’s “if you have to partition why not use Riak”.3 replies 0 retweets 0 likes -
-
Replying to @bascule
@bascule@KirinDave I feel like I have a much better bead on how Redis will misbehave than Cassandra or HBase.3 replies 0 retweets 0 likes
@tqbf @KirinDave FWIW, our mission critical Redises are still using a bunch of CPU and we can't tell why :(
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.