From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 2F0833CB3D for ; Tue, 31 Jan 2017 11:08:49 -0500 (EST) Received: by mail-pf0-x236.google.com with SMTP id f144so107844839pfa.2 for ; Tue, 31 Jan 2017 08:08:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=i8SdTREBTl27IzXqr/g5Jetd7MVi2+V4jNrQjW69vJI=; b=HZHlVJRvcVTTx5Qlj/FdhlciXstj/725BGchV6lhzAcs1cojdCg09evwfkOk49KMuv /tgZ5uTdu+vIAHiggKjaXu96x2Le85cx7nOMLKF1Bv/8IXlldRyyVAXe4+QjKbrSklAP WJ6H8utc1x45xVDqLSDrJzszlaqIfJ8ciXrOEq28N4/XQS/Sf9pEi9dmHiQ7hQAhvbET rnOJCer0Qg1F2PegRTxzJrZmsaDjFGjTIjfzVC0a+fFZJSiCMa9xUbjjISPJRBp0hIrE nnVNxUOX/MQBRc07EcUJnUkjQQTvHBpX36TrfyX3wvrrzt8almW7LDZU1w1q0HwsEdUA rMKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=i8SdTREBTl27IzXqr/g5Jetd7MVi2+V4jNrQjW69vJI=; b=rcLWvUlAlBD8Ga7+WDL1MXqv4MiPC63P0g/nQMflYgAsh/t58UfLI7iIRBuWAQZXDK 9g5vpyLPmNqed7NB7Esjv+Yx7+/otl0/e8xXHNYGr/EJ2UG82yHkzS5xKDtac76LUu+g Ln6swYoTIdOmjuHxf24nYFFfXNXhEJMGvsp/thmZFta26q+hib73RwymZylNE0YKd+Ap IUh+/u+g+VmVauiG80PpL94nzkZh99HNWH6/MVV6Pk/pm5AOXTQRpSQEWRUDoLnDQ2t7 VdNpOWXBEkG+ZX2hAt1lmIhDz91cmsquzKU/Ib1oHYP8wbLPItWwJMPuRvPLU32hJ5nr 878w== X-Gm-Message-State: AIkVDXLvN2ekDe7OPpVgTyqhwG1rsQ7Z9bbzQF9D4Bpt225G7bMmMTSyRihznW7fHTvTsA== X-Received: by 10.98.97.68 with SMTP id v65mr29863406pfb.124.1485878928213; Tue, 31 Jan 2017 08:08:48 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id e127sm42217507pfh.89.2017.01.31.08.08.47 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 31 Jan 2017 08:08:48 -0800 (PST) Date: Tue, 31 Jan 2017 08:08:38 -0800 From: Stephen Hemminger To: Dave Taht Cc: bloat , flent-users@flent.org, "cerowrt-devel@lists.bufferbloat.net" , cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net Message-ID: <20170131080838.488d8f1d@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Cerowrt-devel] [Cake] flent testers wanted prior to next release X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 16:08:49 -0000 On Tue, 20 Dec 2016 11:02:44 -0800 Dave Taht wrote: > Toke has been busy adding new features to the flent network test tool. > I consider it *almost* stable enough for a new release. Some of the > development has been focused on making the flent-gui much faster and > more responsive (as our data sets have got larger), others on > providing better default command line output, and there's other fixes > across the board, including QT5 support. > > In particular, I fear we've broken windows users of flent. I would > dearly like it if some more folk out there using flent could pull the > latest git version and see if there are any new bugs or regressions in > it, any of the the 87 tests, and the plotters, before freezing the > code for a new year's release. > > github: https://github.com/tohojo/flent > main site: https://flent.org/ > > While you are at it, please feel free to stress out any of the flent > servers as a target, give the new cake a shot and compare it against > htb+fq_codel or your aqm of choice, or fiddle with the new wifi code, > and share your data. tcp_nup, tcp_ndown, rrul, rrul_be remain the main > tests, but the square wave one is turning out interesting.... :) > > And if you have any feature requests or bugs to file, please get them > in soon to the github! > > We could also use better documentation and tutorials for use... some > more example scripts leveraging things like the cpu_stats and > qdisc_stats tools, and so on, > > Active public servers include: > > flent-freemont.bufferbloat.net > ( this is colocated with flent-bbr-west which has bbr on by default - an > interesting test might be testing both these servers at the same time > via the rtt_fair* tests from your location) > > flent-dallas.bufferbloat.net > flent-london.bufferbloat.net > flent-tokyo.bufferbloat.net > flent-newark.bufferbloat.net > > There are also netperf-west and netperf-east and netperf-eu and no > doubt a few others. > > We plan to add a few BBR enabled servers over the holidays. > > The changelog so far: > > > - Support PyQt5 in the GUI (and prefer it over PyQt4). If PyQt5 is not > found, fall back to PyQt4. > > > - Add new SummaryFormatter that outputs mean and median values for > each data series. This is the new default formatter, meaning that its > output will be shown after a test run if no other formatter (or plot) > is specified. > > - Support multiprocessing in the GUI. When loading several plots at > once, plotting will now be passed off to separate worker processes. > > This allows plotting to use all the available processors on the > machine, and speeds up loading of many plots tremendously (initial > load is sped up by an order of magnitude). This change also means that > re-plotting on config changes will be done dynamically in the > background, which makes the GUI more responsive. > > - Make text completely black in the default colour scheme. This > increases contrast, and helps legibility, especially on printed > figures. > > > - Some internal code changes: Port command line parser from the old > optparse class to the newer argparse, and fix a bunch of linter > > Has anyone automated or orchestrated flent? I would love to get several projects doing daily build flent runs. Both upstream kernel, net-next, and Intel Clear Linux has nightly build and test. Also Microsoft's internal Linux testing of kernel devices, maybe even the Azure development cycle. Though I doubt those results could be shared.