The speedof.me API probably can be used directly as the measurement of download and upload - you can create a competing download or upload in Javascript using a WebWorker talking to another server that supports the websocket API to force buffer overflow. (sort of poor man's RRUL). The speedof.me API would give you the measured performance, while the other path would just be aan easier to code test load to a source/sink. Not sure that would help, but for a prototype it's not bad.
On Thursday, September 11, 2014 8:42pm, "Jonathan Morton" <chromati...@gmail.com> said: > > On 12 Sep, 2014, at 3:35 am, dpr...@reed.com wrote: > > > Among friends of mine, we can publicize this widely. But those friends > probably would like to see how the measurement would work. > > Could we make use of the existing test servers (running netperf) for that > demonstration? How hard is the protocol to fake in Javascript? > > Or would a netperf-wrapper demonstration suffice? We've already got that, but > we'd need to extract the single-figures-of-merit from the data. > > I wonder if the speedof.me API can already be tricked into doing the right > thing? > > - Jonathan Morton > >
_______________________________________________ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
