carto
/
grpc


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
							<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.17"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<title>GRPC C++: gRPC (Core) Compression Cookbook</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/searchdata.js"></script>
<script type="text/javascript" src="search/search.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
 <tbody>
 <tr style="height: 56px;">
  <td id="projectalign" style="padding-left: 0.5em;">
   <div id="projectname">GRPC C++
   &#160;<span id="projectnumber">1.36.1</span>
   </div>
  </td>
 </tr>
 </tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.17 -->
<script type="text/javascript">
/* @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&amp;dn=gpl-2.0.txt GPL-v2 */
var searchBox = new SearchBox("searchBox", "search",false,'Search');
/* @license-end */
</script>
<script type="text/javascript" src="menudata.js"></script>
<script type="text/javascript" src="menu.js"></script>
<script type="text/javascript">
/* @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&amp;dn=gpl-2.0.txt GPL-v2 */
$(function() {
  initMenu('',true,false,'search.php','Search');
  $(document).ready(function() { init_search(); });
});
/* @license-end */</script>
<div id="main-nav"></div>
<!-- window showing the filter options -->
<div id="MSearchSelectWindow"
     onmouseover="return searchBox.OnSearchSelectShow()"
     onmouseout="return searchBox.OnSearchSelectHide()"
     onkeydown="return searchBox.OnSearchSelectKey(event)">
</div>

<!-- iframe showing the search results (closed by default) -->
<div id="MSearchResultsWindow">
<iframe src="javascript:void(0)" frameborder="0" 
        name="MSearchResults" id="MSearchResults">
</iframe>
</div>

</div><!-- top -->
<div class="PageDoc"><div class="header">
  <div class="headertitle">
<div class="title">gRPC (Core) Compression Cookbook </div>  </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><h1><a class="anchor" id="autotoc_md60"></a>
Introduction</h1>
<p>This document describes compression as implemented by the gRPC C core. See <a class="el" href="compression_8md.html">the</a>full compression specification" for details.</p>
<h2><a class="anchor" id="autotoc_md61"></a>
Intended Audience</h2>
<p>Wrapped languages developers, for the purposes of supporting compression by interacting with the C core.</p>
<h1><a class="anchor" id="autotoc_md62"></a>
Criteria for GA readiness</h1>
<ol type="1">
<li>Be able to set compression at <a href="#per-channel-settings">channel</a>, <a href="#per-call-settings">call</a> and <a href="#per-message-settings">message</a> level. In principle this API should be based on <em>compression levels</em> as opposed to algorithms. See the discussion <a href="#level-vs-algorithms">below</a>.</li>
</ol>
<ol type="1">
<li>Have unit tests covering <a href="https://github.com/grpc/grpc/blob/master/doc/compression.md#test-cases">the cases from the spec</a>.</li>
</ol>
<ol type="1">
<li>Interop tests implemented and passing on Jenkins. The two relevant interop test cases are <a href="https://github.com/grpc/grpc/blob/master/doc/interop-test-descriptions.md#large_compressed_unary">large_compressed_unary</a> and <a href="https://github.com/grpc/grpc/blob/master/doc/interop-test-descriptions.md#server_compressed_streaming">server_compressed_streaming</a>.</li>
</ol>
<h1><a class="anchor" id="autotoc_md63"></a>
Summary Flowcharts</h1>
<p>The following flowcharts depict the evolution of a message, both <em>incoming</em> and <em>outgoing</em>, irrespective of the client/server character of the call. Aspects still not symmetric between clients and servers (e.g. the <a href="https://github.com/grpc/grpc/blob/master/doc/compression.md#compression-levels-and-algorithms">use of compression levels</a>) are explicitly marked. The in-detail textual description for the different scenarios is described in subsequent sections.</p>
<h1><a class="anchor" id="autotoc_md64"></a>
Incoming Messages</h1>
<p><img src="images/compression_cookbook_incoming.png" alt="image" class="inline"/></p>
<h1><a class="anchor" id="autotoc_md65"></a>
Outgoing Messages</h1>
<p><img src="images/compression_cookbook_outgoing.png" alt="image" class="inline"/></p>
<h1><a class="anchor" id="autotoc_md66"></a>
Levels vs Algorithms</h1>
<p>As mentioned in <a href="https://github.com/grpc/grpc/blob/master/doc/compression.md#compression-levels-and-algorithms">the relevant discussion on the spec document</a>, compression <em>levels</em> are the primary mechanism for compression selection <em>at the server side</em>. In the future, it'll also be at the client side. The use of levels abstracts away the intricacies of selecting a concrete algorithm supported by a peer, on top of removing the burden of choice from the developer. As of this writing (Q2 2016), clients can only specify compression <em>algorithms</em>. Clients will support levels as soon as an automatic retry/negotiation mechanism is in place.</p>
<h1><a class="anchor" id="autotoc_md67"></a>
Per Channel Settings</h1>
<p>Compression may be configured at channel creation. This is a convenience to avoid having to repeatedly configure compression for every call. Note that any compression setting on individual <a href="#per-call-settings">calls</a> or <a href="#per-message-settings">messages</a> overrides channel settings.</p>
<p>The following aspects can be configured at channel-creation time via channel arguments:</p>
<h3><a class="anchor" id="autotoc_md68"></a>
Disable Compression &lt;em&gt;Algorithms&lt;/em&gt;</h3>
<p>Use the channel argument key <code>GRPC_COMPRESSION_CHANNEL_ENABLED_ALGORITHMS_BITSET</code> (from <a href="https://github.com/grpc/grpc/blob/master/include/grpc/impl/codegen/compression_types.h"><code>grpc/impl/codegen/compression_types.h</code></a>), takes a 32 bit bitset value. A set bit means the algorithm with that enum value according to <code>grpc_compression_algorithm</code> is <em>enabled</em>. For example, <code>GRPC_COMPRESS_GZIP</code> currently has a numeric value of 2. To enable/disable GZIP for a channel, one would set/clear the 3rd LSB (eg, 0b100 = 0x4). Note that setting/clearing 0th position, that corresponding to <code>GRPC_COMPRESS_NONE</code>, has no effect, as no-compression (a.k.a. <em>identity</em>) is always supported. Incoming messages compressed (ie, encoded) with a disabled algorithm will result in the call being closed with <code>GRPC_STATUS_UNIMPLEMENTED</code>.</p>
<h3><a class="anchor" id="autotoc_md69"></a>
Default Compression &lt;em&gt;Level&lt;/em&gt;</h3>
<p>**(currently, Q2 2016, only applicable for server side channels. It's ignored for clients.)** Use the channel argument key <code>GRPC_COMPRESSION_CHANNEL_DEFAULT_LEVEL</code> (from <a href="https://github.com/grpc/grpc/blob/master/include/grpc/impl/codegen/compression_types.h"><code>grpc/impl/codegen/compression_types.h</code></a>), valued by an integer corresponding to a value from the <code>grpc_compression_level</code> enum.</p>
<h3><a class="anchor" id="autotoc_md70"></a>
Default Compression &lt;em&gt;Algorithm&lt;/em&gt;</h3>
<p>Use the channel argument key <code>GRPC_COMPRESSION_CHANNEL_DEFAULT_ALGORITHM</code> (from <a href="https://github.com/grpc/grpc/blob/master/include/grpc/impl/codegen/compression_types.h"><code>grpc/impl/codegen/compression_types.h</code></a>), valued by an integer corresponding to a value from the <code>grpc_compression_level</code> enum.</p>
<h1><a class="anchor" id="autotoc_md71"></a>
Per Call Settings</h1>
<h2><a class="anchor" id="autotoc_md72"></a>
Compression &lt;strong&gt;Level&lt;/strong&gt; in Call Responses</h2>
<p>The server requests a compression level via initial metadata. The <code>send_initial_metadata</code> <code><a class="el" href="structgrpc__op.html" title="Operation data: one field for each op type (except SEND_CLOSE_FROM_CLIENT which has no arguments)">grpc_op</a></code> contains a <code>maybe_compression_level</code> field with two fields, <code>is_set</code> and <code>compression_level</code>. The former must be set when actively choosing a level to disambiguate the default value of zero (no compression) from the proactive selection of no compression.</p>
<p>The core will receive the request for the compression level and automatically choose a compression algorithm based on its knowledge about the peer (communicated by the client via the <code>grpc-accept-encoding</code> header. Note that the absence of this header means no compression is supported by the client/peer).</p>
<h2><a class="anchor" id="autotoc_md73"></a>
Compression &lt;strong&gt;Algorithm&lt;/strong&gt; in Call Responses</h2>
<p><b>Server should avoid setting the compression algorithm directly</b>. Prefer setting compression levels unless there's a <em>very</em> compelling reason to choose specific algorithms (benchmarking, testing).</p>
<p>Selection of concrete compression algorithms is performed by adding a <code>(GRPC_COMPRESS_REQUEST_ALGORITHM_KEY, &lt;algorithm-name&gt;)</code> key-value pair to the initial metadata, where <code>GRPC_COMPRESS_REQUEST_ALGORITHM_KEY</code> is defined in <a href="https://github.com/grpc/grpc/blob/master/include/grpc/impl/codegen/compression_types.h"><code>grpc/impl/codegen/compression_types.h</code></a>), and <code>&lt;algorithm-name&gt;</code> is the human readable name of the algorithm as given in <a href="https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md">the HTTP2 spec</a> for <code>Message-Encoding</code> (e.g. gzip, identity, etc.). See <a href="https://github.com/grpc/grpc/blob/master/src/core/lib/compression/compression.c"><code>grpc_compression_algorithm_name</code></a> for the mapping between the <code>grpc_compression_algorithm</code> enum values and their textual representation.</p>
<h1><a class="anchor" id="autotoc_md74"></a>
Per Message Settings</h1>
<p>To disable compression for a specific message, the <code>flags</code> field of <code><a class="el" href="structgrpc__op.html" title="Operation data: one field for each op type (except SEND_CLOSE_FROM_CLIENT which has no arguments)">grpc_op</a></code> instances of type <code>GRPC_OP_SEND_MESSAGE</code> must have its <code>GRPC_WRITE_NO_COMPRESS</code> bit set. Refer to <a href="https://github.com/grpc/grpc/blob/master/include/grpc/impl/codegen/compression_types.h"><code>grpc/impl/codegen/compression_types.h</code></a>), </p>
</div></div><!-- contents -->
</div><!-- PageDoc -->
<!-- start footer part -->
<hr class="footer"/><address class="footer"><small>
Generated on Wed Mar 3 2021 19:17:22 for GRPC C++ by &#160;<a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/>
</a> 1.8.17
</small></address>
</body>
</html>