<p>Stepping back, I've updated the TODO and Roadmap for irtt: <a href="https://github.com/peteheist/irtt#todo-and-roadmap">https://github.com/peteheist/irtt#todo-and-roadmap</a></p>
<p>Basically, after a bunch of tasks to solidify and complete things as they stand, I'll try to take on the two biggest weaknesses of irtt:</p>
<ul>
<li>Non-isochronous send schedules and variable packet sizes. This should handle, among other things Dave's "videoconferencing emulation" request or other things.</li>
<li>Improving induced latency and jitter. I may attempt to optimize things for the Linux case by doing the thread scheduling and system calls from C, and handle the rest in Go. I strongly suspect that it's not Go's raw execution speed that adds a bit of latency / jitter, but everything that Go's scheduler does when making system calls. I'll prototype and prove this out first.</li>
</ul>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/tohojo/flent/issues/106#issuecomment-345512621">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AerUv7B6fQfUuiVIxN88l8GJXsYt0CmCks5s4B33gaJpZM4MpJAm">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AerUv72DbTc9yGDkfH2IWA4JGBnr3IAXks5s4B33gaJpZM4MpJAm.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-345512621"></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":"@peteheist in #106: Stepping back, I've updated the TODO and Roadmap for irtt: https://github.com/peteheist/irtt#todo-and-roadmap\r\n\r\nBasically, after a bunch of tasks to solidify and complete things as they stand, I'll try to take on the two biggest weaknesses of irtt:\r\n\r\n- Non-isochronous send schedules and variable packet sizes. This should handle, among other things Dave's \"videoconferencing emulation\" request or other things.\r\n- Improving induced latency and jitter. I may attempt to optimize things for the Linux case by doing the thread scheduling and system calls from C, and handle the rest in Go. I strongly suspect that it's not Go's raw execution speed that adds a bit of latency / jitter, but everything that Go's scheduler does when making system calls. I'll prototype and prove this out first.\r\n"}],"action":{"name":"View Issue","url":"https://github.com/tohojo/flent/issues/106#issuecomment-345512621"}}}</script>