itamarhaber

Excellent deep dive - treasured.

Not that exotic anymore... in not-so-many-months we'll have little things with ARMs all over the planet.

Alley cats never change (should have been a Duran Duran hit IMO)

Indeed it is but the 1st RC is expected within days/weeks so that would be the direction I'd be exploring from now on ;)

Simply awesome dude - I'm betting this will get a lot of love from Redis users.

Nice of you to provide this write-up. Apropos Blogd, have you considered implementing it as a Redis module instead of forking?

Nice stuff, although with the upcoming Redis v4 it makes more sense imo to implement these as bona fide native modules, e.g.: https://github.com/RedisLabsModules/redex/blob/master/README...

One of the, if not the, nicest Redis modules out there so far!

Different org: https://github.com/RedisLabsModules

As modules are still not GA, no. Going forward, modules from the Hub will be available for open source Redis, Redis Cloud and Redis Labs Enterprise Cluster.

Updates pushed online - thanks again.

FoA here - it is gonna be awesome #FTFTW :)

That's one of the ideas. Developers who wish to monetize off their work will be able to do so and immediately have their modules available from the biggest Redis distribution channels.

ty - looking into it

Indeed - http://modules.redis.io will be the open source place and the Redis Labs' Module Hub is at https://redismodules.com

Woohoo!!!

Kudos George!

I second that :)

Not that silly and perfectly doable with the current support for Lua scripts...

I really enjoy the stuff in Redis Watch - anything and everything about Redis: https://redislabs.com/redis-watch-archive

DISCLAIMER: I'm the curator and janitor of the newletter

A single Redis instance uses a single CPU core so yeah, hitting the its limits (no matter how high) is always a possibility. OTOH, there's always the possibility for sharding and clustering a Redis database to scale it up 'n out, thus making "overwhelming" it less trivial.

Redis needs only two nodes on GCE to deliver 1M writes per second: https://redislabs.com/blog/nosql-bar-datastax-aerospike-couc...

Woohoo

I took the liberty of doing a very naive test on my laptop's VM - the results are at https://gist.github.com/itamarhaber/2ed09513ec6f6ae10071.

  Memcached text: 43585 OPS @ 4.58 msec 
  Memcached binary: 40242 OPS @ 4.96 msec
  Redis: 39727 OPS @ 5.03 msec
  Redis, pipeline 4: 131312 OPS @ 6.09 msec

lolz

no questions, only kudos and one of my favorite items in the latest edition of Redis Watch (COOLEST. LOGO. EVER.)

Now it is up.

May you have a long and rot-free life!

Not a good idea, I'm afraid. Your ad-hoc will cause the caching to stutter and the job queues to stagger. Redis is a single-threaded server and shared databases, well, share the same process. The common practice is to use dedicated Redis servers, one for each database. This also has the nice side benefit of allowing you config each as needed (e.g. LRU eviction for cache, persistency for jobs, etc...)

+1