154 lines
14 KiB
HTML
154 lines
14 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: Frequently Asked Questions</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 class="current"><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><a href="files.html"><span>Files</span></a></li>
|
|
</ul>
|
|
</div>
|
|
</div><!-- top -->
|
|
<div class="header">
|
|
<div class="headertitle">
|
|
<div class="title">Frequently Asked Questions</div> </div>
|
|
</div><!--header-->
|
|
<div class="contents">
|
|
<h1><a class="anchor" id="faq-handler-single-channel"></a>
|
|
Can more than one channel per Handler be processed? Alternatively, are multiple Handler instances necessary?</h1>
|
|
<p>One instance of <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1Handler.html">OnixS::CME::MDH::Handler</a> processes market data for a single channel only. Users must create multiple instances of the Handler to process data from multiple channels.</p>
|
|
<p><a class="el" href="group__faq.html#faq-handler-single-channel">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-handler-securities-subscribed"></a>
|
|
Is the Handler implicitly subscribed to all instruments of the specified channel? Will it receive security definitions for all instruments of this channel?</h1>
|
|
<p>Yes, exactly.</p>
|
|
<p><a class="el" href="group__faq.html#faq-handler-securities-subscribed">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-filtering"></a>
|
|
How does instrument/group filtering work? Why would we want to do this?</h1>
|
|
<p>Filtering (instrument selection) is useful when market data required for specific instruments only. Instrument selection is like an inclusive whitelist. E.g., if security A is selected, security-related events (members of <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html" title="Callbacks invoked by Handler to expose market data entities. ">OnixS::CME::MDH::SecurityListener</a>) are raised for security A only.</p>
|
|
<p>If two or more securities are selected, events are triggered only for those securities.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a class="el" href="group__security-selection.html">Selecting Securities of Interest</a></dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-filtering">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-book-consistency"></a>
|
|
How do we know whether the data delivered through onBookAtomicUpdate is the first or last change of a "transaction"? That is, how can it be determined that the order book is valid/consistent/not-crossed after a single onBookAtomicUpdate() call?</h1>
|
|
<p>It is a bit more complicated with book consistency & up-to-date. Please, note that CME does not guarantee 100% book up-to-date on intermediate updates. It is guaranteed only after 'End of XXX quote' market event where XXX is real or implied. So you have to check this field to ensure the book is 100% up-to-date.</p>
|
|
<p>It can be achieved by using book update callbacks of <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html" title="Callbacks invoked by Handler to expose market data entities. ">OnixS::CME::MDH::SecurityListener</a> rather than atomic book update listening. They are publishing the books only on 'End of XXX quotes' market event giving guarantee books are consistent and up-to-date.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html" title="Callbacks invoked by Handler to expose market data entities. ">OnixS::CME::MDH::SecurityListener</a>, <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1MarketDataListener.html">OnixS::CME::MDH::MarketDataListener</a></dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-book-consistency">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-initial-book"></a>
|
|
How to retrieve/receive the initial order book?</h1>
|
|
<p>Any <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#a9a81ad09e17caf95e9d24941dbe7c98b">OnixS::CME::MDH::SecurityListener::onBookUpdate</a> call gives you consistent order book state (except for Natural Refresh mode). If you need book state at startup, you can just get a snapshot at first call.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a class="el" href="group__book-construction-and-copying.html">Constructing And Copying Books</a></dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-initial-book">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-no-market-data"></a>
|
|
After switching the Operating System, even the sample program is no longer able to receive market data (code=NoNetworkActivity). However, I can ping the CME router and iLink server. Any insight or suggestions on what may be going on here?</h1>
|
|
<p>See <a class="el" href="group__connectivity-troubleshooting.html">Connectivity Troubleshooting</a>.</p>
|
|
<p><a class="el" href="group__faq.html#faq-no-market-data">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-cache-limit-exceeded"></a>
|
|
If Handler joins while the market is busy, warnings (code=QueueOverflow) are reported. Is there any possibility to raise the configured limit, if so how?</h1>
|
|
<p>When the Handler performs book recovery, it caches all the data received on incremental feeds. When the market is busy, a number of cached messages may exceed configured limit defined by the <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1HandlerSettings.html#a4269e7bc8e8f468748fcdac54e95436e">OnixS::CME::MDH::HandlerSettings::recoveryQueueMaxSize</a> parameter value. So, to avoid <code>QueueOverflow</code> warnings, it is necessary to increase the value of the noted parameter.</p>
|
|
<p><a class="el" href="group__faq.html#faq-cache-limit-exceeded">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-queue-overflow"></a>
|
|
What is the cause of 'QueueOverflow' warnings?</h1>
|
|
<p>The cause is a violation of received packets sequence (gap) that wasn't restored after the <a class="el" href="classOnixS_1_1CME_1_1MDH_1_1RealtimeFeedSettings.html#a0f6d193c0a194bcc3ac43958f50fad14">OnixS::CME::MDH::RealtimeFeedSettings::outOfOrderPacketMaxInterval</a> number of packets or after the OnixS::CME::MDH::HandlerSettings::lostPacketWaitTime elapsed. Violation of packet sequence can be caused by packets loss on different levels: CME environment issues, network connectivity issues, system or application issues.</p>
|
|
<p>Also, when Handler performs a large-scale recovery due to the gap or while joining market lately, incremental packets are cached. In case of intensive data transmission, queue keeping incremental packets may reach its limit causing a noted warning.</p>
|
|
<p>Please refer to our <a href="http://ref.onixs.biz/lost-multicast-packets-troubleshooting.html">Lost multicast packets troubleshooting guide</a> for more details.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a class="el" href="group__connectivity-troubleshooting.html">Connectivity Troubleshooting</a>.</dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-queue-overflow">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-book-atomic-and-complex-update"></a>
|
|
What's the difference between 'Book Atomic Update' and 'Book Update' events?</h1>
|
|
<p><b>Book Atomic Update</b> (<a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#aadebc2ae366c8636ac275a6d4347cf7e" title="Invoked when atomic book update for. ">OnixS::CME::MDH::SecurityListener::onBookAtomicUpdate</a>) is an <em>elementary action over a book,</em> and usually, <em>there're multiple atomic updates inside a single snapshot or incremental refresh</em>. Also, the book <em>may not be valid between two atomic updates</em>. Only when all atomic updates are processed from the single market event, the book is considered as valid.</p>
|
|
<p><b>Book Update</b> (<a class="el" href="structOnixS_1_1CME_1_1MDH_1_1SecurityListener.html#a9a81ad09e17caf95e9d24941dbe7c98b">OnixS::CME::MDH::SecurityListener::onBookUpdate</a>) are raised exactly at a time when all atomic updates are processed, and the book appears to be <em>valid</em> and <em>up-to-date</em>.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a class="el" href="group__book-self-building.html">Building and Maintaining Books by Yourself</a></dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-book-atomic-and-complex-update">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-price-dividing"></a>
|
|
While processing market data for CME, I noticed that some instruments are divided by 100, others by 10000 and the others are not. How do I determine what value to scale the prices?</h1>
|
|
<p>Security definition sent by Market Data Platform contains fields</p>
|
|
<ul>
|
|
<li>DisplayFactor (tag 9787) - for securities with non-fractional price</li>
|
|
<li>MainFraction (tag 37702) and SubFraction (tag 37703) - for securities with fractional price</li>
|
|
</ul>
|
|
<p>representing the multipliers to convert the CME Globex display price to the conventional price.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a href="http://www.cmegroup.com/confluence/display/EPICSANDBOX/MDP+3.0+-+CME+Globex+Pricing">CME Pricing documentaton</a>.</dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-price-dividing">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-handler-latency"></a>
|
|
Which latency is added by the Handler?</h1>
|
|
<p>Minimal book update latency falls into 100-250 nanoseconds depending on hardware/operating system/network conditions. Please, contact <a href="#" onclick="location.href='mai'+'lto:'+'sal'+'es'+'@on'+'ix'+'s.b'+'iz'; return false;">Onix Sales</a> for most recent official benchmark results.</p>
|
|
<p><a class="el" href="group__faq.html#faq-handler-latency">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-handler-cpu-consumption"></a>
|
|
What is Handler CPU consumption?</h1>
|
|
<p>It depends significantly on many different parameters including network, hardware, operating system environment, market data rate and applied handler settings.</p>
|
|
<p><a class="el" href="group__faq.html#faq-handler-cpu-consumption">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-expected-callback-latency"></a>
|
|
What is the expected maximum latency our callback implementation should have?</h1>
|
|
<p>The smaller, the better. It shall be microseconds to do not impact handler ability to process data on high tickers.</p>
|
|
<p><a class="el" href="group__faq.html#faq-expected-callback-latency">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-error-reporting"></a>
|
|
How are problems with market data indicated (book became invalid)?</h1>
|
|
<p>The Handler reports all errors and warnings through <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1HandlerListener.html#a300fb78746701ace3cc538b94b067685">OnixS::CME::MDH::HandlerListener::onError</a> and <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1HandlerListener.html#ab5e810ce981b513bf72d83fba7aba473">OnixS::CME::MDH::HandlerListener::onWarning</a> callbacks respectively.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a class="el" href="group__error-and-warning-handling.html">Handling Issues Like Errors and Warnings</a></dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-error-reporting">Permanent link to the answer</a></p>
|
|
<h1><a class="anchor" id="faq-detect-packet-issues"></a>
|
|
How can packet issues (back-pressure/queuing) be diagnosed?</h1>
|
|
<p>The Handler allows tracing packets as they are received by active feeds including out-of-order or duplicated packets (in contrast to market data listening which exposes packets passed through session rules). With the help of the new <a class="el" href="structOnixS_1_1CME_1_1MDH_1_1FeedListener.html" title="Listener for feed-related events. ">OnixS::CME::MDH::FeedListener</a> listener, it is possible to write advanced diagnostic services.</p>
|
|
<dl class="section see"><dt>See also</dt><dd><a class="el" href="group__feed-event-listener.html">Listening for Activity on the Feeds</a></dd></dl>
|
|
<p><a class="el" href="group__faq.html#faq-detect-packet-issues">Permanent link to the answer</a> </p>
|
|
</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>
|