From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.toke.dk X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-101.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.1 Received: from mail.toke.dk by mail.toke.dk with LMTP id iC/zMQDXElqdXwAAOr1fkg for ; Mon, 20 Nov 2017 14:22:08 +0100 Received: from web6.sd.eurovps.com (web6.sd.eurovps.com [77.235.54.103]) by mail.toke.dk (Postfix) with ESMTPS id 2867B235F7B for ; Mon, 20 Nov 2017 14:22:07 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=fail reason="key not found in DNS" (0-bit key) header.d=flent.org header.i=@flent.org header.b=bVg4K2HF; dkim=fail reason="signature verification failed" (1024-bit key) header.d=github.com header.i=@github.com header.b=I9LyGy0J DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=flent.org; s=default; h=Sender:Content-Type:Cc:Reply-To:List-Subscribe:List-Help: List-Post:List-Archive:List-Unsubscribe:List-Id:Subject:Mime-Version: References:In-Reply-To:Message-ID:To:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=0n+7cwuuczpvcskunonQHVwTty8xzE3yIl88SS/XaIs=; b=bVg4K2HFX51fz2FmRDruFRC8a0 WV8csVwzjij8qEaZhxdoiGoTWIBlW4VQTGnavNKTOZbRb7+YKtLaVio5MpP4AtgYks1msOiEdTzk2 4V14pRjwmHHB25lqLKACXKasza7q2dWsOYHoboDcrsMXKeO4qILStXTjflXc/sXysLrNrvwTHGSf+ YfClbskJz0RZj2f6FrEzckptGClMTjn8zPzQ/tmk/l4GE6bHLr2+kRChxLUvjV3sHpJmBqgH6xx0w D0ecz2Zi6BbXNzretQnnWmv5TIp2EpiNQOxhEU0tKHqYnxgqGp9VSIRLIWDvIXz8fIsFJr55+mxSE UN9HbSlA==; Received: from [::1] (port=50363 helo=web6.sd.eurovps.com) by web6.sd.eurovps.com with esmtp (Exim 4.89) (envelope-from ) id 1eGm1V-0004cX-0X; Mon, 20 Nov 2017 15:22:05 +0200 Received: from o3.sgmail.github.com ([192.254.112.98]:1709) by web6.sd.eurovps.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1eGm1N-0004UK-Rc for flent-users@flent.org; Mon, 20 Nov 2017 15:22:03 +0200 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=mZDj5wKkfqNLM3BNYaXXOuZQXxA=; b=I9LyGy0JQ7A6f4P+ b2KThDIX45mB4tB/BH4rd69c2M+PCTNcIIJuUdwvl2JQip8Pqf716lP7akKNES5n tILHK9GPHjy8LeFzlxw/w5XQtPHNZ8bxMfClSppUukxCrUJjbbnDUERdDvXuTaCo fGdPJ+qEe+vtBITrZ7wGTsd9CG4= Received: by filter0537p1mdw1.sendgrid.net with SMTP id filter0537p1mdw1-23586-5A12D6CC-8 2017-11-20 13:21:16.431797031 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id ZsroIvDkTI6egws5Rv95jw for ; Mon, 20 Nov 2017 13:21:16.442 +0000 (UTC) Date: Mon, 20 Nov 2017 13:21:16 +0000 (UTC) From: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= To: tohojo/flent Message-ID: In-Reply-To: References: Mime-Version: 1.0 Precedence: list X-GitHub-Sender: tohojo X-GitHub-Recipient: flent-users X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: flent-users@flent.org tracking: X-SG-EID: IRsowsd9yCOJafMG0EWGsh26xBq50lgDrxWUlCCqUntutQCCcaOFwkpUzpsgFyDi6YKxdpD8uEWIa/ lYJrDlylytN9ecNTuqmmSgUv+AEVtFmj9HB1yOp8IZ+gHiw5/GIcRo9QblQwDgP1XKfWpDuiiIftZy SA/XzVNDZlUyXaTIWcT/XlteY2NhcpbZJS+bGTiGvyLjvrM3nmkUSW34mkd5YrzQy/iU26Y//7lKJd UrGtefIOgtxSg9VFMcPrZG Subject: Re: [Flent-users] [tohojo/flent] packet loss stats (#106) X-BeenThere: flent-users@flent.org X-Mailman-Version: 2.1.23 List-Id: Flent discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: tohojo/flent Cc: Comment , flent-users Content-Type: multipart/mixed; boundary="===============5765511400437567710==" Errors-To: flent-users-bounces@flent.org Sender: "Flent-users" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - web6.sd.eurovps.com X-AntiAbuse: Original Domain - toke.dk X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - flent.org X-Get-Message-Sender-Via: web6.sd.eurovps.com: acl_c_authenticated_local_user: mailman/mailman X-Authenticated-Sender: web6.sd.eurovps.com: mailman@flent.org --===============5765511400437567710== Content-Type: multipart/alternative; boundary="--==_mimepart_5a12d6cc550b3_277633fcfe54b8f30123507c"; charset=UTF-8 Content-Transfer-Encoding: 7bit ----==_mimepart_5a12d6cc550b3_277633fcfe54b8f30123507c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Pete Heist writes: >> On Nov 20, 2017, at 1:11 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>=20 >> Pete Heist writes: >>=20 >> > G.711 can be simulated today with `-i 20ms -l 172 -fill rand >> > -fillall`. I do this test pretty often, and I think it would be a good >> > default voip test. >>=20 >> The problem with this is that it also changes the sampling rate. I don't >> necessarily want to plot the latency every 20ms, so I'd have to >> compensate for that in the Flent plotter somehow. Also, a better way to >> deal with loss would be needed. > > > I wondered if/when this would come up=E2=80=A6 Why not plot the latency e= very > 20ms, too dense? For the current plot type (where data points are connected by lines), certainly. It would probably be possible to plot denser data sets by a point cloud type plot, but that would make denser data series harder to read. > I guess even if not, eventually at a low enough interval the round > trip and plotting intervals would need to be decoupled, no matter what > plot type is used. Yeah, exactly. > If we want to minimize flent changes, irtt could optionally produce a > `round_trip_snapshots` (name TBD) array in the json with elements > created at a specified interval (`-si duration` or similar) that would > summarize the data from multiple round trips. For each snapshot, there > would be no timestamps, but the start and end seqnos would be there > (if needed), mean delays and ipdv, counts (or percentages?) of lost, > lost_up or lost_down, etc. I=E2=80=99d need to spec this out, but would > something like this help? Hmm, seeing as we probably want to keep all the data points in the Flent data file anyway, I think we might as well do the sub-sampling in Flent. Just thinning the plots is a few lines of numpy code; just need to figure out a good place to apply it. Handling loss is another matter, but one that I need to deal with anyway. Right now I'm just throwing away lost data points entirely, which loses the lost_{up,down} information. Will fix that and also figure out the right way to indicate losses. -Toke --=20 You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/tohojo/flent/issues/106#issuecomment-345693455= ----==_mimepart_5a12d6cc550b3_277633fcfe54b8f30123507c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Pete Heist <notifications@github.com> writes:

>> On Nov 20, 2017, at 1:11 PM, Toke H=C3=B8iland-J=C3=B8rgensen <= notifications@github.com> wrote:
>>
>> Pete Heist <notifications@github.com> writes:
>>
>> > G.711 can be simulated today with `-i 20ms -l 172 -fill rand<= br> >> > -fillall`. I do this test pretty often, and I think it would = be a good
>> > default voip test.
>>
>> The problem with this is that it also changes the sampling rate. I= don't
>> necessarily want to plot the latency every 20ms, so I'd have t= o
>> compensate for that in the Flent plotter somehow. Also, a better w= ay to
>> deal with loss would be needed.
>
>
> I wondered if/when this would come up=E2=80=A6 Why not plot the latenc= y every
> 20ms, too dense?

For the current plot type (where data points are connected by lines),
certainly. It would probably be possible to plot denser data sets by a
point cloud type plot, but that would make denser data series harder to
read.

> I guess even if not, eventually at a low enough interval the round
> trip and plotting intervals would need to be decoupled, no matter what=
> plot type is used.

Yeah, exactly.

> If we want to minimize flent changes, irtt could optionally produce a<= br> > `round_trip_snapshots` (name TBD) array in the json with elements
> created at a specified interval (`-si duration` or similar) that would=
> summarize the data from multiple round trips. For each snapshot, there=
> would be no timestamps, but the start and end seqnos would be there
> (if needed), mean delays and ipdv, counts (or percentages?) of lost, > lost_up or lost_down, etc. I=E2=80=99d need to spec this out, but woul= d
> something like this help?

Hmm, seeing as we probably want to keep all the data points in the Flent
data file anyway, I think we might as well do the sub-sampling in Flent.
Just thinning the plots is a few lines of numpy code; just need to
figure out a good place to apply it.

Handling loss is another matter, but one that I need to deal with
anyway. Right now I'm just throwing away lost data points entirely,
which loses the lost_{up,down} information. Will fix that and also
figure out the right way to indicate losses.

-Toke

&mda= sh;
You are receiving this because you commented.
Reply to this e= mail directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5a12d6cc550b3_277633fcfe54b8f30123507c-- --===============5765511400437567710== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Flent-users mailing list Flent-users@flent.org http://flent.org/mailman/listinfo/flent-users_flent.org --===============5765511400437567710==--