From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] httpd stats
Date: Thu, 14 Nov 2002 12:24:53 -0500 [thread overview]
Message-ID: <66cdf2f6ea5152627ff2053888286405@plan9.bell-labs.com> (raw)
i don't know about numbers, but plan9.bell-labs.com has
been slashdotted a few times and not fallen over.
when we put up the 4e distribution, we got really
hammered, but by many large downloads rather
than many many small downloads. the bottleneck
turned out to be the connection to the file server.
now we keep all the distribution files in a (large) ramfs
cache.
next reply other threads:[~2002-11-14 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 17:24 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 14:02 Sam
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=66cdf2f6ea5152627ff2053888286405@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).