New Twitter account for Redis news
The new Twitter account @redisfeed will be used to provide informations about Redis new releases, critical bugs, and everything else is important for people that are using or plan to use Redis. Please follow us! http://twitter.com/redisfeed
Comments
New site look improved a bit.
Now it’s like a mix between a twitter timeline and a blog. I fixed the RSS feed, but still could be generated better than that. Well the point is that as far as I’ve the min needed to improve it in the future will be easy and fun.
p.s. yes the layout …
Ask your questions on Stack Overflow if you wish
Hey, since I’m no longer active on Twitter, that was a channel where from time to time I replied to requests from users, I’m now making sure I reply to a few questions on Stack Overflow every day, lurking on the “Redis” tag:
http://stackoverflow.com/q…
Random victim on Twitter
These are the real victims of flamewars:
“After the recent affair with @antirez’s blogpost, I’m seriously considering forgoing further usage of #Redis in all my projects.” (@nathell)
Obvious considerations:
1) Somebody will be happy about this as th…
New 2.6 MONITOR behaviour with transactions
The commit message says it all:
Fix MULTI / EXEC rendering in MONITOR output.
Before of this commit it used to be like this:
MULTI
EXEC
… actual commands of the transaction …
Because after all that is the nat…
Next days…
I’m going to be a bit away from Redis code and this blog as I need to freaking focus on finishing the video talks for the Redis Conference that is very near at this point…
I’m also tuning and testing the final bits into 2.6 to make sure to release i…
Almost 1000 followers for @redisfeed in a couple of days
On twitter I read a few concerns about inability to read what I think about tech non-redis topics. First of all, thanks to everybody interested in my thoughts :) Second, this blog is exactly the place where I’ll post everything like that.
So:
@redisf…
Estimating Redis memory usage
Good article by Josiah Carlson on Redis memory usage estimation, including copy-on-write worst case during BGSAVE:
https://groups.google.com/d/msg/redis-db/02oq_DNZA3s/l_uEwDT3d4sJ
Comments