2 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01//EN">
5 <link type=
"text/css" rel=
"stylesheet" href=
"style.css" />
12 <img style=
"border:none" alt=
"Redis Documentation" src=
"redis.png">
16 <div id=
"pagecontent">
18 <!-- This is a (PRE) block. Make sure it's left aligned or your toc title will be off. -->
19 <b>Pipelining: Contents
</b><br> <a href=
"#Pipelining (DRAFT)">Pipelining (DRAFT)
</a>
22 <h1 class=
"wikiname">Pipelining
</h1>
29 <h1><a name=
"Pipelining (DRAFT)">Pipelining (DRAFT)
</a></h1>A client library can use the same connection in order to issue multiple commands. But Redis supports
<b>pipelining
</b>, so multiple commands can be sent to the server with a single write operation by the client, without need to read the server reply in order to issue the next command. All the replies can be read at the end.
<br/><br/>Usually Redis server and client will have a very fast link so this is not very important to support this feature in a client implementation, still if an application needs to issue a very large number of commands in s short time, using pipelining can be much faster.
<br/><br/>Please read the
<a href=
"ProtocolSpecification.html">ProtocolSpecification
</a> if you want to learn more about the way Redis
<a href=
"SupportedLanguages.html">clients
</a> and the server communicate.
<br/><br/>Pipelining is one of the
<a href=
"Speed.html">Speed
</a> <a href=
"Features.html">Features
</a> of Redis, you can also check the support for
<a href=
"MultiBulkCommands.html">send and receive multiple values in a single command
</a>.