From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] fremont.nq.taht.net is ready for rpm testing
Date: Tue, 19 Apr 2022 17:36:36 +0200 [thread overview]
Message-ID: <DD2CCD0A-4915-49F0-A4DF-413357B54BF7@gmx.de> (raw)
In-Reply-To: <CAA93jw70ZuYEcUapnr-VPJh04o47EBSMiHLPKfAsdNjB4_AN=A@mail.gmail.com>
Mmmh:
user@work-horse:~/CODE/goresponsiveness$ ./networkQuality --config fremont.nq.taht.net --port 443 --path config
04-19-2022 15:33:36 UTC Go Responsiveness to fremont.nq.taht.net:443...
Error: Saturation could not be completed in time and no provisional rates could be accessed. Test failed.
Might be too far away from Fremont?
Regards
Sebastian
> On Apr 19, 2022, at 17:20, Dave Taht via Rpm <rpm@lists.bufferbloat.net> wrote:
>
> Example of use:
>
> I don't have an osx box to test with...
>
> davetaht@penguin:~/goresponsiveness$ ./goresponsiveness --config
> fremont.nq.taht.net --port 443 --path config
> 04-19-2022 15:13:12 UTC Go Responsiveness to fremont.nq.taht.net:443...
> Download: 39.447 Mbps ( 4.931 MBps), using 12 parallel connections.
> Upload: 1.000 Mbps ( 0.125 MBps), using 24 parallel connections.
> (really crazy to open that many as I've mentioned)
>
> Total RTTs measured: 5
> RPM: 30
>
> ...
>
> I built a worldwide apache2 cluster.... not fully deployed yet: one
> trick is you need to use a full chain on a letsencrypt cert on the
> server, I don't know if that's the case on other cert types
>
> Apache config
>
> #SSLCertificateFile "/etc/letsencrypt/live/fremont.nq.taht.net/cert.pem"
> SSLCertificateFile "/etc/letsencrypt/live/fremont.nq.taht.net/fullchain.pem"
> SSLCertificateKeyFile "/etc/letsencrypt/live/fremont.nq.taht.net/privkey.pem"
>
> # kvetches
> * the large file is REALLY large. Ran me out of disk. It doesn't need
> to be that stinking large.
> * seq -f "x" doesn't work on my linux, results in a 1 character file.
> Is that meant to be just one 'x" elsewhere or
> a string of numbers? xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx compresses too well.
> *
>
> My cluster is ALSO flent capable, so as to calibrate flent or irtt
> based tests against it.
>
> I'm using a CNAME for it, which is kind of a clever trick I think
> in measuring DNS latency....
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
next prev parent reply other threads:[~2022-04-19 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 15:20 Dave Taht
2022-04-19 15:36 ` Sebastian Moeller [this message]
2022-04-19 15:53 ` Dave Taht
2022-04-19 20:41 ` Sebastian Moeller
2022-04-20 2:25 ` Will Hawkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DD2CCD0A-4915-49F0-A4DF-413357B54BF7@gmx.de \
--to=moeller0@gmx.de \
--cc=dave.taht@gmail.com \
--cc=rpm@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox