From: ron minnich <rminnich@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] scaling on TCP socket connections
Date: Thu, 9 Mar 2023 16:23:40 -0800 [thread overview]
Message-ID: <CAP6exYKgnSx4Q4kHijjZAaUN6GZaGXL=2omfA9tFFh8y9DtA0w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Ca. 1981, if memory serves, having even small numbers of TCP connections
was not common.
I was told at some point that Sun used UDP for NFS for that reason. It was
a reasonably big deal when we started to move to TCP for NFS ca 1990 (my
memory of the date -- I know I did it on my own for SunOS as an experiment
when I worked at the SRC -- it seemed to come into general use about that
time).
What kind of numbers for TCP connections would be reasonable in 1980, 90,
2000, 2010?
I sort of think I know, but I sort of think I'm probably wrong.
[-- Attachment #2: Type: text/html, Size: 650 bytes --]
next reply other threads:[~2023-03-10 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 0:23 ron minnich [this message]
2023-03-10 0:42 ` [TUHS] " David Arnold
2023-03-10 0:48 ` Warner Losh
2023-03-10 0:59 ` Tom Lyon
2023-03-10 1:24 ` Lawrence Stewart
2023-03-10 1:32 ` Larry McVoy
2023-03-10 10:14 ` Ralph Corderoy
2023-03-10 15:10 ` Larry McVoy
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='CAP6exYKgnSx4Q4kHijjZAaUN6GZaGXL=2omfA9tFFh8y9DtA0w@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=tuhs@tuhs.org \
/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).