<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p><br>
</p>
<p>My private definition:<br>
</p>
<p>Hard real time -> 100% requests/jobs/processes must be
completed before deadline</p>
<p>Soft real time -> N% requests/jobs/processes must be completed
before deadline, where N < 100%,</p>
<p> so we can/must accept that some jobs will not be finished on
time.<br>
</p>
<p><br>
</p>
<p>And few question:</p>
<p>1. Erlang VM is running on Virtual Machine on bare metal?<br>
</p>
<p>2. What you erlang process really do? Can you show us some code?<br>
</p>
<p><br>
</p>
<p>Regards</p>
<p>Aleksander Nycz<br>
</p>
<br>
<div class="moz-cite-prefix">W dniu 2017-10-20 o 14:00, Avinash
Dhumane pisze:<br>
</div>
<blockquote type="cite"
cite="mid:CAGPCG6WTcQeTKxxEUz_EVz6bK0MAePOuBB03aE_VHb_n574LjQ@mail.gmail.com">
<div dir="ltr">I have programmed high-frequency trading
application in Erlang and comparing its reaction performance in
the live market with other competing applications (mostly, in
C).
<div><br>
</div>
<div>It has been a consistent observation that my Erlang
application lags substantially behind the competing
applications. In fact, it never matched the reaction time of
the so-called "slowest" C application in the market. </div>
<div><br>
</div>
<div>The benchmark reaction time is about 5 microseconds. It is
the time elapsed between tick to order. That is, the
difference between the timestamps when I receive the tick
(market event) from the mailbox of my process and when I
submit the TCP send call on my order.</div>
<div><br>
</div>
<div>My process maintains the market depths of the securities
and when my desired price (as a function of best buyers and/or
sellers on multiple legs of the order) is observed, I compute
the order terms and submit. </div>
<div><br>
</div>
<div>The entire computation and communication (with the market)
takes place within the single process and there are no
collaborating processes (hence, no inter-process messaging;
not even ETS). Still, the reaction time is in the order of 20
to 60 microseconds - that is, nowhere closer to the benchmark
reaction time (5 microseconds).</div>
<div><br>
</div>
<div>What I wish to hear from the experienced people on this
forum here is whether I am missing on something in my Erlang
code, or should I just go ahead and program in C.</div>
<div><br>
</div>
<div>Thanks.</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Aleksander Nycz
Chief Designer
Telco_021 BSS R&D
Comarch SA
Phone: +48 17 785 5909
Mobile: +48 691 464 275
website: <a class="moz-txt-link-abbreviated" href="http://www.comarch.pl">www.comarch.pl</a></pre>
</body>
</html>