82 lines
17 KiB
HTML
82 lines
17 KiB
HTML
<!-- HTML header for doxygen 1.8.11-->
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<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.11"/>
|
|
<title>OnixS C++ CME Market Data Handler: Pages/LowLatencyBestPractices.md Source File</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="doxygen.css" rel="stylesheet" type="text/css" />
|
|
<link href="onixs-doxygen.css" rel="stylesheet" type="text/css"/>
|
|
<script type="text/javascript">
|
|
$(window).scroll(function() {
|
|
if ($(this).scrollTop() > 1)
|
|
{
|
|
$('header').addClass("sticky");
|
|
}
|
|
else
|
|
{
|
|
$('header').removeClass("sticky");
|
|
}
|
|
});
|
|
</script>
|
|
</head>
|
|
<body>
|
|
<header>
|
|
<div id="titlearea">
|
|
<table cellspacing="0" cellpadding="0">
|
|
<tbody>
|
|
<tr style="height: 56px;">
|
|
<td id="projectlogo"><a href="http://www.onixs.biz"><img alt="Logo" src="onixs.svg"/></a></td>
|
|
<td style="padding-left: 0.5em;">
|
|
<div id="projectname">OnixS C++ CME Market Data Handler
|
|
 <span id="projectnumber">4.8.0.10</span>
|
|
</div>
|
|
<div id="projectbrief">API documentation</div>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</header>
|
|
<div id="wrapper">
|
|
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
|
|
<!-- end header part -->
|
|
<!-- Generated by Doxygen 1.8.11 -->
|
|
<div id="navrow1" class="tabs">
|
|
<ul class="tablist">
|
|
<li><a href="index.html"><span>Home</span></a></li>
|
|
<li><a href="modules.html"><span>Contents</span></a></li>
|
|
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
|
|
<li><a href="annotated.html"><span>Classes</span></a></li>
|
|
<li class="current"><a href="files.html"><span>Files</span></a></li>
|
|
</ul>
|
|
</div>
|
|
<div id="navrow2" class="tabs2">
|
|
<ul class="tablist">
|
|
<li><a href="files.html"><span>File List</span></a></li>
|
|
<li><a href="globals.html"><span>File Members</span></a></li>
|
|
</ul>
|
|
</div>
|
|
</div><!-- top -->
|
|
<div class="header">
|
|
<div class="headertitle">
|
|
<div class="title">Pages/LowLatencyBestPractices.md</div> </div>
|
|
</div><!--header-->
|
|
<div class="contents">
|
|
<a href="LowLatencyBestPractices_8md.html">Go to the documentation of this file.</a><div class="fragment"><div class="line"><a name="l00001"></a><span class="lineno"> 1</span> \addtogroup low-latency-best-practices </div><div class="line"><a name="l00002"></a><span class="lineno"> 2</span> </div><div class="line"><a name="l00003"></a><span class="lineno"> 3</span> \brief Uncovers how to configure the Handler to achieve maximal </div><div class="line"><a name="l00004"></a><span class="lineno"> 4</span> performance characteristics and lowest processing latency.</div><div class="line"><a name="l00005"></a><span class="lineno"> 5</span> </div><div class="line"><a name="l00006"></a><span class="lineno"> 6</span> The given topic uncovers how to configure the Handler in order to </div><div class="line"><a name="l00007"></a><span class="lineno"> 7</span> achieve maximal performance characteristics and lowest processing </div><div class="line"><a name="l00008"></a><span class="lineno"> 8</span> latency.</div><div class="line"><a name="l00009"></a><span class="lineno"> 9</span> </div><div class="line"><a name="l00010"></a><span class="lineno"> 10</span> \section configure-logging-for-low-latency Configuring Logging Subsystem</div><div class="line"><a name="l00011"></a><span class="lineno"> 11</span> </div><div class="line"><a name="l00012"></a><span class="lineno"> 12</span> Under normal conditions, the Handler logs important events and market data </div><div class="line"><a name="l00013"></a><span class="lineno"> 13</span> transmitted by MDP into a log file. As far as logging entries represent </div><div class="line"><a name="l00014"></a><span class="lineno"> 14</span> textual information, binary data like incoming market data packets are </div><div class="line"><a name="l00015"></a><span class="lineno"> 15</span> encoded using base64-encoding before stored in a log. That adds extra time </div><div class="line"><a name="l00016"></a><span class="lineno"> 16</span> to a processing cycle. Finally, if the Logger implementation stores its </div><div class="line"><a name="l00017"></a><span class="lineno"> 17</span> data into a file, that may be a relatively slow operation.</div><div class="line"><a name="l00018"></a><span class="lineno"> 18</span> </div><div class="line"><a name="l00019"></a><span class="lineno"> 19</span> If the users want to eliminate slowdowns caused by flushing data to filesystem </div><div class="line"><a name="l00020"></a><span class="lineno"> 20</span> and/or extra encoding operations, they can disable logging by binding instance </div><div class="line"><a name="l00021"></a><span class="lineno"> 21</span> of the OnixS::CME::MDH::NullLogger class to the Handler. In such case </div><div class="line"><a name="l00022"></a><span class="lineno"> 22</span> log events are not constructed by the Handler, and nothing is logged at </div><div class="line"><a name="l00023"></a><span class="lineno"> 23</span> all. </div><div class="line"><a name="l00024"></a><span class="lineno"> 24</span> </div><div class="line"><a name="l00025"></a><span class="lineno"> 25</span> \section configure-threads-for-low-latency Turning Up Working Threads</div><div class="line"><a name="l00026"></a><span class="lineno"> 26</span> </div><div class="line"><a name="l00027"></a><span class="lineno"> 27</span> Market data processing is done asynchronously by using working threads. </div><div class="line"><a name="l00028"></a><span class="lineno"> 28</span> Under normal conditions, threads are executed on any processor available </div><div class="line"><a name="l00029"></a><span class="lineno"> 29</span> in the system. That may have negative influence on overall performance </div><div class="line"><a name="l00030"></a><span class="lineno"> 30</span> due to unnecessary thread context switching. </div><div class="line"><a name="l00031"></a><span class="lineno"> 31</span> </div><div class="line"><a name="l00032"></a><span class="lineno"> 32</span> To avoid switching threads between processors, the Feed Engine as a </div><div class="line"><a name="l00033"></a><span class="lineno"> 33</span> manager of working threads, allows to establish processor affinity for </div><div class="line"><a name="l00034"></a><span class="lineno"> 34</span> each working thread:</div><div class="line"><a name="l00035"></a><span class="lineno"> 35</span> </div><div class="line"><a name="l00036"></a><span class="lineno"> 36</span> ~~~{.cpp}</div><div class="line"><a name="l00037"></a><span class="lineno"> 37</span> </div><div class="line"><a name="l00038"></a><span class="lineno"> 38</span> FeedEngineSettings feSettings1;</div><div class="line"><a name="l00039"></a><span class="lineno"> 39</span> FeedEngineSettings feSettings2;</div><div class="line"><a name="l00040"></a><span class="lineno"> 40</span> </div><div class="line"><a name="l00041"></a><span class="lineno"> 41</span> // Scheduling Feed Engines to use different processors.</div><div class="line"><a name="l00042"></a><span class="lineno"> 42</span> </div><div class="line"><a name="l00043"></a><span class="lineno"> 43</span> feSettings1.threadAffinity().insert(1);</div><div class="line"><a name="l00044"></a><span class="lineno"> 44</span> feSettings2.threadAffinity().insert(2);</div><div class="line"><a name="l00045"></a><span class="lineno"> 45</span> </div><div class="line"><a name="l00046"></a><span class="lineno"> 46</span> ~~~</div><div class="line"><a name="l00047"></a><span class="lineno"> 47</span> </div><div class="line"><a name="l00048"></a><span class="lineno"> 48</span> In addition to the ability to manipulate thread affinity for working </div><div class="line"><a name="l00049"></a><span class="lineno"> 49</span> threads of the Feed Engine, it also provides a set of events triggered </div><div class="line"><a name="l00050"></a><span class="lineno"> 50</span> by working threads at the beginning of processing and before ending </div><div class="line"><a name="l00051"></a><span class="lineno"> 51</span> a processing loop. See \ref feed-engine-events for more information.</div><div class="line"><a name="l00052"></a><span class="lineno"> 52</span> </div><div class="line"><a name="l00053"></a><span class="lineno"> 53</span> With the help of working threads events, it is possible to perform </div><div class="line"><a name="l00054"></a><span class="lineno"> 54</span> more advanced thread turning like updating thread priority:</div><div class="line"><a name="l00055"></a><span class="lineno"> 55</span> </div><div class="line"><a name="l00056"></a><span class="lineno"> 56</span> ~~~{.cpp}</div><div class="line"><a name="l00057"></a><span class="lineno"> 57</span> </div><div class="line"><a name="l00058"></a><span class="lineno"> 58</span> using namespace OnixS::CME::MDH;</div><div class="line"><a name="l00059"></a><span class="lineno"> 59</span> </div><div class="line"><a name="l00060"></a><span class="lineno"> 60</span> struct ThreadPriorityManager : FeedEngineListener</div><div class="line"><a name="l00061"></a><span class="lineno"> 61</span> {</div><div class="line"><a name="l00062"></a><span class="lineno"> 62</span>  void onFeedEngineThreadBegin(const FeedEngine&)</div><div class="line"><a name="l00063"></a><span class="lineno"> 63</span>  {</div><div class="line"><a name="l00064"></a><span class="lineno"> 64</span>  SetThreadPriority(</div><div class="line"><a name="l00065"></a><span class="lineno"> 65</span>  GetCurrentThread(),</div><div class="line"><a name="l00066"></a><span class="lineno"> 66</span>  THREAD_PRIORITY_TIME_CRITICAL);</div><div class="line"><a name="l00067"></a><span class="lineno"> 67</span>  }</div><div class="line"><a name="l00068"></a><span class="lineno"> 68</span> };</div><div class="line"><a name="l00069"></a><span class="lineno"> 69</span> </div><div class="line"><a name="l00070"></a><span class="lineno"> 70</span> FeedEngineSettings feSettings;</div><div class="line"><a name="l00071"></a><span class="lineno"> 71</span> ThreadPriorityManager priorityManager;</div><div class="line"><a name="l00072"></a><span class="lineno"> 72</span> </div><div class="line"><a name="l00073"></a><span class="lineno"> 73</span> FeedEngine feedEngine(feSettings, &priorityManager); </div><div class="line"><a name="l00074"></a><span class="lineno"> 74</span> </div><div class="line"><a name="l00075"></a><span class="lineno"> 75</span> ~~~</div><div class="line"><a name="l00076"></a><span class="lineno"> 76</span> </div><div class="line"><a name="l00077"></a><span class="lineno"> 77</span> \section decreasing-data-waiting-time Decreasing Time Handler Spends on Waiting for Incoming Data</div><div class="line"><a name="l00078"></a><span class="lineno"> 78</span> </div><div class="line"><a name="l00079"></a><span class="lineno"> 79</span> When the Handler accomplishes processing of the previously </div><div class="line"><a name="l00080"></a><span class="lineno"> 80</span> received market data, it initiates reception of new incoming </div><div class="line"><a name="l00081"></a><span class="lineno"> 81</span> data if it is available in the feed. In reality, data packets </div><div class="line"><a name="l00082"></a><span class="lineno"> 82</span> do not come each after another, but there's a certain time </div><div class="line"><a name="l00083"></a><span class="lineno"> 83</span> interval between two neighbor packets. Pauses between incoming </div><div class="line"><a name="l00084"></a><span class="lineno"> 84</span> packets cause the Feed Engine bound to the Handler to suspend </div><div class="line"><a name="l00085"></a><span class="lineno"> 85</span> activities and sleep in a kernel while waiting for incoming data. </div><div class="line"><a name="l00086"></a><span class="lineno"> 86</span> As a result, data and an execution code can be ejected from a </div><div class="line"><a name="l00087"></a><span class="lineno"> 87</span> processor's cache. That brings to the fact that the next iteration </div><div class="line"><a name="l00088"></a><span class="lineno"> 88</span> of processing loop is performed slower compare to the previous </div><div class="line"><a name="l00089"></a><span class="lineno"> 89</span> one. The Feed Engine provides the </div><div class="line"><a name="l00090"></a><span class="lineno"> 90</span> OnixS::CME::MDH::FeedEngineSettings::dataWaitTime parameter, which </div><div class="line"><a name="l00091"></a><span class="lineno"> 91</span> value defines the time the Feed Engine spends in I/O operation while </div><div class="line"><a name="l00092"></a><span class="lineno"> 92</span> waiting for incoming data. Reducing a value of the noted parameter </div><div class="line"><a name="l00093"></a><span class="lineno"> 93</span> increases the number of wake-ups, and thus reduces the probability for </div><div class="line"><a name="l00094"></a><span class="lineno"> 94</span> the Feed Engine to be thrown out of a processor's cache. If the parameter </div><div class="line"><a name="l00095"></a><span class="lineno"> 95</span> is set to zero, the Feed Engine just checks for data availability, but </div><div class="line"><a name="l00096"></a><span class="lineno"> 96</span> does not enter into a kernel for sleep. The drawback of reducing waiting </div><div class="line"><a name="l00097"></a><span class="lineno"> 97</span> time is an increase of processor consumption (up to 100% in case of zero </div><div class="line"><a name="l00098"></a><span class="lineno"> 98</span> parameter value).</div><div class="line"><a name="l00099"></a><span class="lineno"> 99</span> </div><div class="line"><a name="l00100"></a><span class="lineno"> 100</span> \section suppress-coping-for-low-latency Suppressing Market Data Copying </div><div class="line"><a name="l00101"></a><span class="lineno"> 101</span> </div><div class="line"><a name="l00102"></a><span class="lineno"> 102</span> Under normal conditions, the Handler effectively utilizes internal structures </div><div class="line"><a name="l00103"></a><span class="lineno"> 103</span> used to keep incoming market data. Packets and messages are re-used once the </div><div class="line"><a name="l00104"></a><span class="lineno"> 104</span> Handler processes the contained data. Therefore, no data is allocated during </div><div class="line"><a name="l00105"></a><span class="lineno"> 105</span> a real-time market data processing. </div><div class="line"><a name="l00106"></a><span class="lineno"> 106</span> </div><div class="line"><a name="l00107"></a><span class="lineno"> 107</span> However, data may be copied within callbacks, which the Handler invokes </div><div class="line"><a name="l00108"></a><span class="lineno"> 108</span> as listeners for various market data events. Thus, when a book is copied, </div><div class="line"><a name="l00109"></a><span class="lineno"> 109</span> that assumes memory allocation and thus has a negative effect on performance </div><div class="line"><a name="l00110"></a><span class="lineno"> 110</span> and latency. Copying should be minimized or strategies with preallocation </div><div class="line"><a name="l00111"></a><span class="lineno"> 111</span> should be used to improve the results.</div><div class="line"><a name="l00112"></a><span class="lineno"> 112</span> </div><div class="line"><a name="l00113"></a><span class="lineno"> 113</span> For example, book snapshots can be constructed of a certain capacity capable </div><div class="line"><a name="l00114"></a><span class="lineno"> 114</span> of storing a particular number of price levels. Constructing book snapshots with </div><div class="line"><a name="l00115"></a><span class="lineno"> 115</span> initial capacity, sufficient to hold books of maximal possible depth, eliminates </div><div class="line"><a name="l00116"></a><span class="lineno"> 116</span> reallocations. </div></div><!-- fragment --></div><!-- contents -->
|
|
<!-- HTML footer for doxygen 1.8.11-->
|
|
<!-- start footer part -->
|
|
<footer>
|
|
<hr class="footer"/>
|
|
<address class="footer">
|
|
<small>© <a href="http://www.onixs.biz">Onix Solutions [On<span class="corporate-orange">i</span>x<span class="corporate-orange">S</span>]</a>. All rights reserved.</small>
|
|
</address>
|
|
</footer>
|
|
</div> <!-- wrapper -->
|
|
</body>
|
|
</html>
|