<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Market Data on Inorderly.com</title>
    <link>https://inorderly.com/tags/market-data/</link>
    <description>Recent content in Market Data on Inorderly.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://inorderly.com/tags/market-data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Merging Two Lossy Market Data Feeds Into One Tick Stream With Exact Gaps</title>
      <link>https://inorderly.com/merging-two-lossy-market-data-feeds-into-one-tick-stream-with-exact-gaps/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://inorderly.com/merging-two-lossy-market-data-feeds-into-one-tick-stream-with-exact-gaps/</guid>
      <description>&lt;p&gt;Exchanges send market data twice, over two lines usually called A and B. Each line drops a packet now and then, and rarely the same one. Take both, keep the first copy of each tick, and you get a fuller feed than either line alone. That&amp;rsquo;s the theory. The merge code is where it gets awkward.&lt;/p&gt;&#xA;&lt;p&gt;This worked example sends 150,000 ticks for three symbols over two lines. Each line loses about 2% of its ticks at random. Line A also goes quiet for four seconds and line B for three, at different times. Line B runs a few milliseconds behind A. In the end 143,458 ticks came on both lines, and 84 came on neither.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
