Redis at Disqus
bretthoerner.com
Redis at Disqus
1–10 of 42 posts
Re: Redis at Disqus
#2I'm thinking about doing a second post with some actual code (some parts may be specific to Python, Django, and Celery) if anyone is interested.
Re: Redis at Disqus
#3I'm thinking about doing a second post with some actual code (some parts may be specific to Python, Django, and Celery) if anyone is interested.
Sure, although at least for me, these posts are most useful for:
1. showing the different kinds of applications people are using redis for;
2. as individual anecdotes that are slowly-but-surely adding up to real data.
Re: Redis at Disqus
#4I'm thinking about doing a second post with some actual code (some parts may be specific to Python, Django, and Celery) if anyone is interested.
I'm definitely interested.
Also, out of curiosity, what do you use to render the actual charts? I'm working on an analytics package and can't decide on a charting engine that is clientside and reasonably performant.
Re: Redis at Disqus
#5I'm thinking about doing a second post with some actual code (some parts may be specific to Python, Django, and Celery) if anyone is interested.
This was a great write up. Redis and the community would benefit from having more writeups like this, detailing different successful real world ways to use it. One can read the Redis documentation and imagine many uses for its different data structures and commands, but to read about tried-and-working practices is fantastic. Of particular use, in my opinion, is seeing key naming/organization schemes that people are using effectively.
I personally would love to see the code for these and other use cases.
Re: Redis at Disqus
#6I'm thinking about doing a second post with some actual code (some parts may be specific to Python, Django, and Celery) if anyone is interested.
I'm definitely interested. Also, out of curiosity, what do you use to render the actual charts? I'm working on an analytics package and can't decide on a charting engine that is clientside and reasonably performant.
A mixture of (mostly) Flot with a touch of Raphael. I am but a lowly backend developer, I'll try to get my colleague dz to comment on the hows and whys.
Re: Redis at Disqus
#7I'm thinking about doing a second post with some actual code (some parts may be specific to Python, Django, and Celery) if anyone is interested.
Sure, although at least for me, these posts are most useful for: 1. showing the different kinds of applications people are using redis for; 2. as individual anecdotes that are slowly-but-surely adding up to real data .
Agreed, those are the same reasons I was happy to see the posts that came well before mine. People that know me well know I will poke holes in everything. We didn't decide on Redis (over tried and true PostgreSQL) for nothing. (We have also used and do use other NoSQL when truly applicable.) I love seeing smart use cases for new DBs.
Re: Redis at Disqus
#8Thank you for this post. This is what we need as a community to improve: use cases, and useful criticisms when things don't work well, so that we can find new strategies.
It's cool to see that Redis works well for many things, but it will be even cooler if diskstore, or any other approach, can made Redis more accessible even when the performance gain of being in-RAM is not enough for some kind of applications to justify the costs.
We are also working at cluster and faster .rdb persistence. So there are interesting things going, but fortunately we will have something new and stable in a few hours, as 2.2.0 stable is going live in very little time :)
Re: Redis at Disqus
#9We have been using it for sessions (amongst tons of other stuff) at Shopify for half a year and found that we didn't have problems with increasing memory after we started setting expiration bits on the session keys.
Re: Redis at Disqus
#10Thank you for this post. This is what we need as a community to improve: use cases, and useful criticisms when things don't work well, so that we can find new strategies. It's cool to see that Redis works well for many things, but it will be even cooler if diskstore, or any other approach, can made Redis more accessible even when the performance gain of being in-RAM is not enough for some kind of applications to just…
Yeah, we can't wait for diskstore. If you imagine the analytics use case for a moment: super high speed is great, but I'd imagine 99% of the read requests don't ask for anything older than a month. Older data could easy be pushed out to disk, saving us a lot of RAM. For now we can still operate pretty easily in RAM (we have a few machines dedicated to analytics and they're just storing counters or sets of small values), but it'd be great to know we can grow a lot more without needing to put more of our shards on their own physical machines.
We already run the latest from the 2.2 branch, I can/should go into how easy that is in a followup.