From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil+venti performance question
Date: Sat, 9 May 2015 21:55:18 -0700 [thread overview]
Message-ID: <d6fc2233547eb3cd551d8d8ce22112ee@brasstown.quanstro.net> (raw)
In-Reply-To: <c4cac4ae3086ef46e7cdcd173378c504@brasstown.quanstro.net>
for what it's worth, the original newreno work tcp does not have the mtu
bug. on a 8 processor system i have around here i get
bwc; while() nettest -a 127.1
tcp!127.0.0.1!40357 count 100000; 819200000 bytes in 1.505948 s @ 519 MB/s (0ms)
tcp!127.0.0.1!47983 count 100000; 819200000 bytes in 1.377984 s @ 567 MB/s (0ms)
tcp!127.0.0.1!53197 count 100000; 819200000 bytes in 1.299967 s @ 601 MB/s (0ms)
tcp!127.0.0.1!61569 count 100000; 819200000 bytes in 1.418073 s @ 551 MB/s (0ms)
however, after fixing things so the initial cwind isn't hosed, i get a little better story:
bwc; while() nettest -a 127.1
tcp!127.0.0.1!54261 count 100000; 819200000 bytes in .5947659 s @ 1.31e+03 MB/s (0ms)
boo yah! not bad for trying to clean up some constants.
- erik
next prev parent reply other threads:[~2015-05-10 4:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 9:32 KADOTA Kyohei
2015-05-04 16:10 ` Anthony Sorace
2015-05-04 18:11 ` Aram Hăvărneanu
2015-05-04 18:51 ` David du Colombier
2015-05-05 14:29 ` Sergey Zhilkin
2015-05-05 15:05 ` Charles Forsyth
2015-05-05 15:38 ` David du Colombier
2015-05-05 22:23 ` Charles Forsyth
2015-05-05 22:29 ` cinap_lenrek
2015-05-05 22:33 ` David du Colombier
2015-05-05 22:53 ` Aram Hăvărneanu
2015-05-06 20:55 ` David du Colombier
2015-05-06 21:17 ` Charles Forsyth
2015-05-06 21:26 ` David du Colombier
2015-05-06 21:28 ` David du Colombier
2015-05-06 22:28 ` Charles Forsyth
2015-05-07 3:35 ` erik quanstrom
2015-05-07 6:15 ` David du Colombier
2015-05-07 13:17 ` erik quanstrom
2015-05-08 16:13 ` David du Colombier
2015-05-08 16:39 ` Charles Forsyth
2015-05-08 17:16 ` David du Colombier
2015-05-08 19:24 ` David du Colombier
2015-05-08 20:03 ` Steve Simon
2015-05-08 21:19 ` Bakul Shah
2015-05-09 14:43 ` erik quanstrom
2015-05-09 17:25 ` Lyndon Nerenberg
2015-05-09 17:30 ` Devon H. O'Dell
2015-05-09 17:35 ` Lyndon Nerenberg
2015-05-09 21:54 ` Devon H. O'Dell
2015-05-09 18:20 ` Bakul Shah
2015-05-09 3:11 ` cinap_lenrek
2015-05-09 5:59 ` lucio
2015-05-09 16:26 ` cinap_lenrek
2015-05-09 16:23 ` erik quanstrom
2015-05-10 4:55 ` erik quanstrom [this message]
2015-05-10 5:07 ` erik quanstrom
2015-05-10 17:57 ` David du Colombier
2015-05-10 20:18 ` erik quanstrom
2015-05-10 20:19 ` cinap_lenrek
2015-05-10 20:51 ` erik quanstrom
2015-05-10 21:34 ` cinap_lenrek
2015-05-11 1:23 ` erik quanstrom
2015-05-09 16:59 ` erik quanstrom
2015-05-06 22:35 ` Steven Stallion
2015-05-06 23:47 ` Charles Forsyth
2015-05-07 3:38 ` erik quanstrom
2015-05-07 3:43 ` erik quanstrom
2015-05-05 15:07 ` KADOTA Kyohei
2015-05-05 14:47 ` KADOTA Kyohei
2015-05-05 15:46 ` steve
2015-05-05 15:54 ` David du Colombier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6fc2233547eb3cd551d8d8ce22112ee@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).