title: How redis pipe-lining works in pyredis?
body: <p>I am trying to understand, how pipe lining in redis works? According to one blog I read, For this code</p>
  
  <pre><code>Pipeline pipeline = jedis.pipelined();
  long start = System.currentTimeMillis();
  for (int i = 0; i &lt; 100000; i++) {
      pipeline.set("" + i, "" + i);
  }
  List&lt;Object&gt; results = pipeline.execute();
  </code></pre>
  
  <p><code>
  Every call to pipeline.set() effectively sends the SET command to Redis (you can easily see this by setting a breakpoint inside the loop and querying Redis with redis-cli). The call to pipeline.execute() is when the reading of all the pending responses happens.
  </code></p>
  
  <p>So basically, when we use pipe-lining, when we execute any command like set above, the command gets executed on the server but we don't collect the response until we executed, pipeline.execute(). </p>
  
  <p>However, according to the documentation of pyredis,
  <code>
  Pipelines are a subclass of the base Redis class that provide support for buffering multiple commands to the server in a single request.
  </code></p>
  
  <p>I think, this implies that, we use pipelining, all the commands are buffered and are sent to the server, when we execute pipe.execute(), so this behaviour is different from the behaviour described above.</p>
  
  <p>Could someone please tell me what is the right behaviour when using pyreids?</p>