Skip to main content

REDIS

When somebody asks us to create a web application, the software requirements will be Apache, Mysql, PhP(LAMP where L stands for Linux). Imagine an application which stores data in main memory instead of disk, this will increase your application performance tremendously. One such application is Redis. Redis stores data on memory instead of disk and will periodically sync with the disks(if necessary).
Why Redis?:
  • Redis will be faster as it keeps data on memory. I read somewhere Memory is like disk and disk is like tape for redis.
  • Redis allows lot of data structures. Basically its a NOSQL database(http://en.wikipedia.org/wiki/NoSQL) . They dont support table or database schema we use traditionally. For them everything is key value pair as in hashmap. Redis allows a key to have values of types- string, set, sorted set, list, hashmap. To understand each data structure and the command they support, have a look at http://simonwillison.net/static/2010/redis-tutorial/
  • Lot of  web apps will be easier to code, as complex operations like sorting, union, aggregation can be done by redis itself
Do Redis follow ACID?
  • As of now, if redis server is crashed and data is not synced with the disk then consistency of data will be an issue
  • Redis server is a single threaded program, so no concurrency issues.
  • If you want a client to make a transaction, multi and exec commands in redis will take care of that. Unlike other databases there is no locking mechanisms involved during transaction. When a client performs exec, server wont get commands from other clients till all command queued for this transaction are done.
  • Single thread can reduce scalability of Redis. Redis supports slaves where a client can read from master and slaves but writes should first affect the master and then synced across the clients. So time consuming operations like sort can be moved to the slaves.
Some Cool Commands to Try Out:
  • BLPOP and BRPOP are some good operations that one always do on queues. Say I am waiting on a queue for a representative to pick up my call. So once a representative comes available, BLPOP will return the representative to the guy who waits for a longer time. No application logic is actually needed
  • Multi and Exec, they support transactions
Where To start?:
  • Install redis (apt-get or yum) or get a free redis instance at http://redis4you.com
  • Almost all languages support redis client coding(for Java download Jedis jar, for Ruby try redis-rb gem). For complete list check at http://redis.io
Start developing web apps without database if your data will fit in memory

Comments

Popular posts from this blog

Lessons from Memory

Started debugging an issue where Linux started calling OOM reaper despite tons of memory is used as Linux cached pages. My assumption was if there is a memory pressure, cache should shrink and leave way for the application to use. This is the documented and expected behavior. OOM reaper is called when few number of times page allocation has failed consequently. If for example mysql wants to grow its buffer and it asks for a page allocation and if the page allocation fails repeatedly, kernel invokes oom reaper. OOM reaper won't move out pages, it sleeps for some time and sees if kswapd or a program has freed up caches/application pages. If not it will start doing the dirty job of killing applications and freeing up memory. In our mysql setup, mysql is the application using most of the Used Memory, so no other application can free up memory for mysql to use. Cached pages are stored as 2 lists in Linux kernel viz active and inactive.
More details here
https://www.kernel.org/doc/gorman…

How we have systematically improved the roads our packets travel to help data imports and exports flourish

This blog post is an account of how we have toiled over the years to improve the throughput of our interDC tunnels. I joined this company around 2012. We were scaling aggressively then. We quickly expanded to 4 DCs with a mixture of AWS and colocation. Our primary DC is connected to all these new DCs via IPSEC tunnels established from SRX. The SRX model we had, had an IPSEC throughput of 350Mbps. Around December 2015 we saturated the SRX. Buying SRX was an option on the table. Buying one with 2Gbps throughput would have cut the story short. The tech team didn't see it happening.

I don't have an answer to the question, "Is it worth spending time in solving a problem if a solution is already available out of box?" This project helped us in improving our critical thinking and in experiencing the theoretical network fundamentals on live traffic, but also caused us quite a bit of fatigue due to management overhead. Cutting short the philosophy, lets jump to the story.

De…

Walking down the Memory Lane!!!

This post is going to be an account of  few trouble-shootings I did recently to combat various I/O sluggishness.
Slow system during problems with backup
We have a NFS mount where we push backups of our database daily. Due to some update to the NFS infra, we started seeing throughput of NFS server drastically affected. During this time we saw general sluggishness in the system during backups. Even ssh logins appeared slower. Some boxes had to be rebooted due to this sluggishness as they were too slow to operate on them. First question we wanted to answer, does NFS keep writing if the server is slow? The slow server applied back pressure by sending small advertised window(TCP) to clients. So clients can't push huge writes if server is affected. Client writes to its page cache. The data from page cache is pushed to server when there is a memory pressure or file close is called. If server is slow, client can easily reach upto dirty_background_ratio set for page cache in sysctl. This di…