Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: John Cowan <cowan@ccil.org>, ron minnich <rminnich@gmail.com>,
	COFF <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: the wheel of reincarnation goes sideways
Date: Sat, 11 Mar 2023 15:32:12 -0500	[thread overview]
Message-ID: <CAEoi9W4E9xvJDZEaYke2zf88tHvGQD9Gafk4FvExNPJLb=rhsQ@mail.gmail.com> (raw)
In-Reply-To: <20230309200932.GK9225@mcvoy.com>

On Thu, Mar 9, 2023 at 3:09 PM Larry McVoy <lm@mcvoy.com> wrote:
> On Thu, Mar 09, 2023 at 02:55:44PM -0500, Dan Cross wrote:
> > On Wed, Mar 8, 2023 at 8:22???PM John Cowan <cowan@ccil.org> wrote:
> > > On Wed, Mar 8, 2023 at 2:53???PM Dan Cross <crossd@gmail.com> wrote:
> > >> But the
> > >> 3090 was really more like a distributed system than the Athlon box
> > >> was, with all sorts of offload capabilities. For that matter, a
> > >> thousand users probably _could_ telnet into the Athlon system. With
> > >> telnet in line mode, it'd probably even be decently responsive.
> > >
> > > I find that difficult to believe.  It seems too high by an order of magnitude.
> >
> > I'm not going to claim it would be zippy, but I do think it would work
> > acceptably.
> >
> > Suppose that 1000 users telnet'ed into the x86 machine, but remained
> > essentially idle; what resources would that consume? We'd have 1000
> > open TCP connections, a thousand shell processes, a thousand
> > telnetd's, etc.
>
> The early Unix code really did not like stuff like this.  Lots of linear
> scans through what were assumed to be short lists.  I still remember an
> SGI Challenge being brought to it's knees by a bunch of racks of modems.
> The same machine could move a ton of data but not when it was being
> forced through a zillion sockets.

Oh for sure I wouldn't try it on a VAX or PDP-11. I'm a bit surprised
by the SGI thing, to be honest, but only a bit: as you say, I think
that was just before the big push to make Unix really scalable.

> Linux seems well past that problem but it's possible that back in the
> Athlon days it still sucked.  I pinged Linus, if he remembers when the
> kernel got taught to scale on sockets I'll report back.

Thanks, I'm curious what he says.

        - Dan C.

  reply	other threads:[~2023-03-11 20:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAP6exY+05fStBtpZGd2HeeNf21fNXeKUTwBV0h5-1YczwF+tew@mail.gmail.com>
2023-03-08 19:52 ` [COFF] Re: [TUHS] " Dan Cross
2023-03-08 20:18   ` [COFF] " Tom Ivar Helbekkmo via COFF
2023-03-09  1:22   ` [COFF] Re: [TUHS] " John Cowan
2023-03-09 19:55     ` Dan Cross
2023-03-09 20:09       ` Larry McVoy
2023-03-11 20:32         ` Dan Cross [this message]
2023-03-11 23:28       ` Bakul Shah
     [not found]   ` <ZA+gxAePDMWK6StD@straylight.ringlet.net>
2023-03-13 22:34     ` Dan Cross
2023-07-05 21:48       ` Dan Cross
2023-07-05 23:58         ` Grant Taylor via COFF
2023-07-06  1:02           ` Dave Horsfall
2023-07-06 16:47             ` Grant Taylor via COFF
2023-07-06  2:35           ` Dan Cross
2023-07-06  4:18           ` Robert Stanford via COFF
2023-07-06 16:53             ` Grant Taylor via COFF
2023-07-06 17:54               ` Adam Thornton
2023-07-09 14:55           ` Michael Parson
2023-08-01  9:52             ` Michael Cardell Widerkrantz
2023-08-01  9:49         ` Michael Cardell Widerkrantz
2023-08-01 15:55           ` Dan Cross
2023-08-01 16:27             ` Grant Taylor via COFF
2023-08-02 16:07               ` Dan Cross
2023-08-02 20:58                 ` Grant Taylor via COFF
2023-08-02 21:16                   ` Dan Cross

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='CAEoi9W4E9xvJDZEaYke2zf88tHvGQD9Gafk4FvExNPJLb=rhsQ@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=coff@tuhs.org \
    --cc=cowan@ccil.org \
    --cc=lm@mcvoy.com \
    --cc=rminnich@gmail.com \
    /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).