Redis vs MySQL Benchmarks

In this article, we would be discussing the performance benchmarks of Redis and MySQL. To begin with, we would start with the introduction and installation of Redis over Ubuntu Machine. Then we would move towards the benchmarking between these two.

Introduction to Redis:

According to the official website, Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker. Actually, Redis is an advanced key-value store. It is literally super fast with amazingly high throughput as it can perform approximately 110000 SETs per second, about 81000 GETs per second. It also supports a very rich set of data types to store. As a matter of fact, Redis keeps the data in-memory every time but also persistent on-disk database. So, it comes with a trade-off: Amazing speed with the size limit on datasets (as per memory). In this article, to have some benchmarks in comparison to MySQL, we would be using Redis as a caching engine only.

Installation of Redis over Ubuntu:

In this section, we would be discussing the steps required to install/configure the Redis over ubuntu machine. Here is the stepwise approach for this:

Installation and Configuration of Redis over Ubuntu:

To start with, run the following commands:

 sudo apt update  
 sudo apt install redis-server

These commands would update the apt package and install the Redis over your Ubuntu machine.

Now, As a matter of fact, to enable Redis being used as a Service, you need to configure it by updating the supervised directive present inside the configuration file of Redis. You can easily find the configuration file here:

 sudo vi /etc/redis/redis.conf

By default, the supervised directive is set to “no”. You need to set it to: systemd . After updating, this section of configuration file would look like something similar to this:

 ################################# GENERAL #####################################  
 # By default Redis does not run as a daemon. Use 'yes' if you need it.  
 # Note that Redis will write a pid file in /var/run/ when daemonized.  
 daemonize yes  
 # If you run Redis from upstart or systemd, Redis can interact with your  
 # supervision tree. Options:  
 #  supervised no   - no supervision interaction  
 #  supervised upstart - signal upstart by putting Redis into SIGSTOP mode  
 #  supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET  
 #  supervised auto  - detect upstart or systemd method based on  
 #            UPSTART_JOB or NOTIFY_SOCKET environment variables  
 # Note: these supervision methods only signal "process is ready."  
 #    They do not enable continuous liveness pings back to your supervisor.  
 supervised systemd  
 # If a pid file is specified, Redis writes it where specified at startup  
 # and removes it at exit.  
 # When the server runs non daemonized, no pid file is created if none is  
 # specified in the configuration. When the server is daemonized, the pid file  
 # is used even if not specified, defaulting to "/var/run/".  
 # Creating a pid file is best effort: if Redis is not able to create it  
 # nothing bad happens, the server will start and run normally.  
 pidfile /var/run/redis/  
 # Specify the server verbosity level.  
 # This can be one of:  
 # debug (a lot of information, useful for development/testing)  
 # verbose (many rarely useful info, but not a mess like the debug level)  
 # notice (moderately verbose, what you want in production probably)

Enabling Password Authentication:

Configuring the Redis with password authentication is not mandatory though, but it is super important (and easy too) as it enables the security factor over Redis. Configuring our Redis server with the password is super easy and can be done through the same configuration file as mentioned above. So, open the configuration file and look for requirepass directive.  You would that line is commented by default, just uncomment that and enter your password there. The configuration file would look similar to this:

 # Require clients to issue AUTH  before processing any other  
 # commands. This might be useful in environments in which you do not trust  
 # others with access to the host running redis-server.  
 # This should stay commented out for backward compatibility and because most  
 # people do not need auth (e.g. they run their own servers).  
 # Warning: since Redis is pretty fast an outside user can try up to  
 # 150k passwords per second against a good box. This means that you should  
 # use a very strong password otherwise it will be very easy to break.  
 requirepass yourpasswordhere  
 # Command renaming.  
 # It is possible to change the name of dangerous commands in a shared  
 # environment. For instance the CONFIG command may be renamed into something  
 # hard to guess so that it will still be available for internal-use tools  
 # but not available for general clients.  
 # Example:  
 # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52

Save this file now and to have the changes reflected over Redis, restart the Redis Service by using the following command:

 sudo systemctl restart redis.service

Installation of PHPRedis over Ubuntu:

Now, to enable your PHP code to use Redis as a service:

  • Run the following command to install PHPRedis extension:
sudo apt-get install php-redis
  • Add the following line to your php.ini file:


  • With MySQL Only:
    • Randomly generate a key between [1, 10000] and search for that key in MySQL database.
    • Would take the note of the time it has taken to do so.
    • Would take the time sample to process n number of such requests while increasing n gradually as 1, 10, 100, 1000, 10000, 100000, 1000000, 1000000.
  • With MySQL and Redis:
    • Randomly generate a key between [1, 10000].
    • Would check if that key is already present/stored on our Redis.
      • If it is present on Redis, we would not hit MySQL.
      • If it is not present on Redis, we would search for that key on our MySQL database and store that key to Redis. 
    • Would take the note of the time it has taken to do so.
    • Would take the time sample to process n number of such requests while increasing n gradually as 1, 10, 100, 1000, 10000, 100000, 1000000, 1000000.

Source Code:

MySQL Only Source Code :

(When we try to fetch key from MySQL only)


MySQL and Redis Source Code :

(When we try to fetch key from Redis first and then from MySQL if we are unable to find that key on Redis)

 for($i = 1; $i <= 10000000; $i = $i *10) {  
      $startTime = microtime(true);  
      for($j = 1; $j <= $i; $j++) {  
           $rand = rand(1, 100000);  
           if(!$client->exists($rand)) {  
                $client->set($rand, $rand);  
                $sql = "SELECT VALUE from data WHERE `key` = $rand";            
                if (!mysqli_query($con, $sql)) {  
                  echo "Error: " . $sql . "" . mysqli_error($con);  
      $endTime = microtime(true);  
      file_put_contents('/home/ayush/Desktop/temp/blog/redis.log', $i . ',' . ($endTime - $startTime) . "n" , FILE_APPEND);  


Graphical Representation :

Graphical Representation : Redis vs MySQL Benchmark

Conclusion :

As it can be easily seen from graphical representation given above, as the number of requests increases significantly, Redis starts outperforming by a significant margin. Hence, using a caching engine like Redis along with your database is a good idea if the number of requests processed is huge. 

Recommended Articles:

If your learning appetite is still left, you are suggested to read below articles:


Source link


Popular posts from this blog

لماذا يحتاج الذكاء الاصطناعي دائمًا إلى الرقابة البشرية ، لا يهم مدى ذكائه

102 Christmas Greeting Cards Collection 6 Unique Animal Designs with Envelopes for Winter Merry Christmas Season, Holiday Giving, Xmas Cute Gifts Cards