From: William Gunnells <gunnells@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] drawterm stuck
Date: Wed, 15 Jul 2020 10:02:30 -0700 [thread overview]
Message-ID: <EE77BC03-8724-43FC-94A0-335C505B26DA@gmail.com> (raw)
In-Reply-To: <CAFSF3XMqjVrRow4RxKf=Pg-JBBTCdSrdXZFsumZ2pJFQXFkcHw@mail.gmail.com>
For such genius and beautiful OS why a slow web server. It kind of doesn’t make sense. Let me know if I’m missing something. Even if its file based shouldn’t there be some level of speed. Like hash tables seem to be extremely fast for lookup. Is it because they wrote httpd in one or two days?
Would it be better to have httpd dedicated to its own CPU and serve other files somewhere else. Serve files on a beefy server. Or am I thinking about that wrong. Should httpd be together? How does that work?
I realize I have a lot to re-learn about this. But I’m very interested.
Surely this should be faster than some python based Django server running gunicorn?
> On Jul 15, 2020, at 6:43 AM, hiro <23hiro@gmail.com> wrote:
>
> to call something slow in such vague way is unscientific at best, and
> you seem agree it's slow with heavy loads.
>
> i claim that it's good enough, and i feel like you're saying the exact
> same thing, what is unfair about what i said, or where do we even
> disagree?
next prev parent reply other threads:[~2020-07-15 17:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 23:02 [9front] " William Gunnells
2020-07-14 0:21 ` hiro
2020-07-14 0:25 ` Amavect
2020-07-14 0:28 ` hiro
2020-07-14 0:34 ` hiro
2020-07-15 6:05 ` [9front] " William Gunnells
2020-07-15 8:15 ` hiro
2020-07-15 13:21 ` Steve Simon
2020-07-15 13:43 ` hiro
2020-07-15 17:02 ` William Gunnells [this message]
2020-07-15 17:13 ` Kurt H Maier
2020-07-15 17:43 ` hiro
2020-07-15 19:10 ` ori
2020-07-17 10:51 ` Ethan Gardener
-- strict thread matches above, loose matches on Subject: below --
2020-07-13 2:48 William Gunnells
2020-07-13 22:24 ` [9front] " Kurt H Maier
2020-07-13 22:47 ` William Gunnells
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=EE77BC03-8724-43FC-94A0-335C505B26DA@gmail.com \
--to=gunnells@gmail.com \
--cc=9front@9front.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).