<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.DefaultFontHxMailStyle
{mso-style-name:"Default Font HxMail Style";
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-IN link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span class=DefaultFontHxMailStyle><span style='font-size:14.0pt'>The market is indeed partitioned into several multicast streams, and each stream replicated, to cover for tick-loss, backed up by a tcp-based recovery server.<o:p></o:p></span></span></p><p class=MsoNormal><span class=DefaultFontHxMailStyle><span style='font-size:14.0pt'><o:p> </o:p></span></span></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:zxq9@zxq9.com">zxq9</a><br><b>Sent: </b>10 April 2021 12:22 PM<br><b>To: </b><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br><b>Subject: </b>Re: gen_udp:recv()</p></div><p class=MsoNormal><span class=DefaultFontHxMailStyle><span style='font-size:14.0pt'><o:p> </o:p></span></span></p><p class=MsoNormal>On 2021/04/10 15:47, Avinash Dhumane wrote:</p><p class=MsoNormal>> The “tick-to-order” indeed needs to be /vertically/ partitioned so that </p><p class=MsoNormal>> the ticks (market movements) do not sit in the queue waiting to be </p><p class=MsoNormal>> attended. More so because the ticks arrive in the bursts; the next </p><p class=MsoNormal>> microsecond might bring no tick, or just one tick, or ten, or hundred, </p><p class=MsoNormal>> or might even eight hundred.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Why are the ticks not partitioned by type? Is it only possible to </p><p class=MsoNormal>receive ALL ticks available in the market at a single address:port? This </p><p class=MsoNormal>seems... very weird and not what I've seen in HFT, at least.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-Craig</p><p class=MsoNormal><span class=DefaultFontHxMailStyle><span style='font-size:14.0pt'><o:p> </o:p></span></span></p></div></body></html>