Pete Heist &lt;notifications@github.com&gt; writes:<br>
<br>
&gt; An update:<br>
&gt;<br>
&gt; - JSON is working, sample attached in case there are comments /<br>
&gt; wishes.<br>
<br>
Lots of data; don&#39;t think I&#39;ll parse all of it in Flent. My thought<br>
would be to save:<br>
<br>
For each data point: RTT, OWD (in both directions), IPDV.<br>
For the whole test:<br>
- Min/max/mean/median RTT values.<br>
- Packet size and/or bit rate<br>
- Most of the params object, probably<br>
<br>
A few comments about the data format:<br>
<br>
- I&#39;m guessing all values are nanoseconds? Are the absolute times in<br>
  UTC?<br>
<br>
- The data points are missing sequence numbers; makes it hard to infer<br>
  loss, and to relate IPDV to RTT values.<br>
  <br>
- Why are the IPDV values in a separate array?<br>
<br>
- Some of the &#39;params&#39; are not terribly useful:<br>
  - What are the local and remote addresses of? Is this where the server<br>
    listens? I&#39;m guessing the client doesn&#39;t connect to 0.0.0.0 at<br>
    least... Would be better to know the values that were actually used.<br>
<br>
  - Similarly, it would be more useful to know whether packets were actually sent<br>
    as IPv4 or IPv6, rather than what was selected.<br>
<br>
- Which fields are guaranteed to be present and which can be blank?<br>
<br>
- What is the send and receive rates? Are they always the same? And in<br>
  which direction? Do they include packet loss?<br>
<br>
- I sort of get why there are so many time stamps in the beginning, but<br>
  I think &#39;first_send_time/first_sent_time&#39; is bound to be confusing at<br>
  some point; is it really necessary to include both? I&#39;m assuming those<br>
  are timestamps on each side of the send() call?<br>
<br>
&gt; - Median (where possible) and stddev are working.<br>
<br>
Cool.<br>
<br>
&gt; - pflag adds 160K to executable, passing for now.<br>
<br>
Yeah, the binary size of Go apps is a PITA. Is this stripped size? Flent<br>
can obviously work with both styles of flags, I just personally thing<br>
the Go defaults are annoying; just be aware that once you release,<br>
changing is going to break backwards compatibility.<br>
<br>
-Toke<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/tohojo/flent/issues/106#issuecomment-332144583">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AerUv-uC3XB5kdqMsa1cMcjcaZkOaCnDks5smMa6gaJpZM4MpJAm">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AerUv6dLRmCmd5hsP-VaMDadTCc8E77uks5smMa6gaJpZM4MpJAm.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/tohojo/flent/issues/106#issuecomment-332144583"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/tohojo/flent","title":"tohojo/flent","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/tohojo/flent"}},"updates":{"snippets":[{"icon":"PERSON","message":"@tohojo in #106: Pete Heist \u003cnotifications@github.com\u003e writes:\n\n\u003e An update:\n\u003e\n\u003e - JSON is working, sample attached in case there are comments /\n\u003e wishes.\n\nLots of data; don't think I'll parse all of it in Flent. My thought\nwould be to save:\n\nFor each data point: RTT, OWD (in both directions), IPDV.\nFor the whole test:\n- Min/max/mean/median RTT values.\n- Packet size and/or bit rate\n- Most of the params object, probably\n\nA few comments about the data format:\n\n- I'm guessing all values are nanoseconds? Are the absolute times in\n  UTC?\n\n- The data points are missing sequence numbers; makes it hard to infer\n  loss, and to relate IPDV to RTT values.\n  \n- Why are the IPDV values in a separate array?\n\n- Some of the 'params' are not terribly useful:\n  - What are the local and remote addresses of? Is this where the server\n    listens? I'm guessing the client doesn't connect to 0.0.0.0 at\n    least... Would be better to know the values that were actually used.\n\n  - Similarly, it would be more useful to know whether packets were actually sent\n    as IPv4 or IPv6, rather than what was selected.\n\n- Which fields are guaranteed to be present and which can be blank?\n\n- What is the send and receive rates? Are they always the same? And in\n  which direction? Do they include packet loss?\n\n- I sort of get why there are so many time stamps in the beginning, but\n  I think 'first_send_time/first_sent_time' is bound to be confusing at\n  some point; is it really necessary to include both? I'm assuming those\n  are timestamps on each side of the send() call?\n\n\u003e - Median (where possible) and stddev are working.\n\nCool.\n\n\u003e - pflag adds 160K to executable, passing for now.\n\nYeah, the binary size of Go apps is a PITA. Is this stripped size? Flent\ncan obviously work with both styles of flags, I just personally thing\nthe Go defaults are annoying; just be aware that once you release,\nchanging is going to break backwards compatibility.\n\n-Toke\n"}],"action":{"name":"View Issue","url":"https://github.com/tohojo/flent/issues/106#issuecomment-332144583"}}}</script>