<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii">
<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:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:228732758;
mso-list-type:hybrid;
mso-list-template-ids:1087130702 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:854154928;
mso-list-template-ids:-1471108270;}
@list l2
{mso-list-id:1498182409;
mso-list-template-ids:-742384744;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">Hello All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">We have a requirement in our platform to serve a few specific URI with a tight performance requirement on the turnaround time (latency).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">One such example is the telemetry sensor metric URI which has power, thermal data can have a max turnaround time of 500ms.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">The current bmcweb design uses only a single thread to serve all URI requests/responses.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">If bmcweb is processing a huge amount of data (which is common for aggregation URIs) then other requests would get blocked and their latency time would get impacted. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">Here I am referring to the time bmcweb takes to prepare the JSON response after it has got the data from the backend service.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">In our platform, we see that power thermal metric URI can take more than 500ms when it’s requested in parallel to other aggregation URI which have huge response data.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">To solve this problem, we thought of a couple of solutions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:#0E101A;mso-list:l2 level1 lfo2"><span style="mso-ligatures:none">To introduce multi-threading support in bmcweb.<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="text-indent:.25in"><span style="color:#0E101A;mso-ligatures:none">Does anyone have any experience/feedback on making this work?<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:.25in"><span style="color:#0E101A;mso-ligatures:none">Is there any strong reason not to have multi-threading support in bmcweb other than general guidelines to avoid threads?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"> <o:p></o:p></span></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="color:#0E101A;margin-left:0in;mso-list:l2 level1 lfo2">
<span style="mso-ligatures:none">To use a reverse proxy like <b>nginx</b> as the front end to redirect a few URIs to a new application server.<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="text-indent:.25in"><span style="color:#0E101A;mso-ligatures:none">Here the idea is to develop a new application server to serve the URIs which have strong latency requirements and route the rest of the URIs to bmcweb.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"> Has anyone experienced any limitations with nginx on openBmc platforms (w.r.t performance, memory footprint, etc)?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"> We also have the requirement to support SSE, Is there any known limitation to make such a feature work with nginx?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">Any other suggestion or solution to the problem we are solving to meet our performance requirement with bmcweb? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0E101A;mso-ligatures:none">Rohit PAI<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>