> On 13 Oct, 2016, at 06:22, Dave Taht wrote:
>
> I still might quibble, but a trimmed mean makes more sense than just a mean.
>
> Problem I always have is bloat is biased always towards the end of a test.
> Here,
> at 1gbit, it took nearly 20 seconds to start going boom.
It is done
under the trimmed mean method, that would be a "C" grade result.
On Thu, Oct 13, 2016 at 11:46 AM, jb wrote:
> Actually I think the concept I need is the trimmed mean.
> throwing away the highest couple of values (lowest couple are not to be
> thrown away because
On Wed, Oct 12, 2016 at 8:32 AM, Jim Gettys wrote:
> All I can say is I bow down to your persistence...
The .debs are airtime-8 for a reason. I kept bisecting until I
bothered to boot into a normal kernel and realized that my main test
box had broken in the move during the
All I can say is I bow down to your persistence...
Congratulations!
- Jim
On Wed, Oct 12, 2016 at 11:18 AM, Dave Taht wrote:
> Which I just wrote up here:
>
> http://blog.cerowrt.org/post/real_results/
>
> Warning: includes a dancing cat
Which I just wrote up here:
http://blog.cerowrt.org/post/real_results/
Warning: includes a dancing cat video!
My principal goal was to make sure *they didn't crash*, and I got
carried away. .. we seem to have a problem with the local TCP stack
in some cases and I went through some hell with
This has major bloat happening at the end of the upload test. Which
worries me - here, at a gbit.
http://www.dslreports.com/speedtest/5284047
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
___