Subject: Re: [9front] Two file servers sharing an auth server
Date: Fri, 04 Nov 2022 00:09:56 -0700 [thread overview]
Message-ID: <83E1A1F40327CC6C521C846162693736@thinktankworkspaces.com> (raw)
Wow. I'm really interested in learning more about this. I kind of figured performance would be better
local rather than served remotely. I might want to dig into this further and I'm curious about
concurrency. Can multiple rc-httpd services be started to handle concurrency?
Examples greatly welcomed
What about non-script apps. I was really interested in some of the web features golang has and if it will work well on another node
Quoth sirjofri <email@example.com>:
> 03.11.2022 21:59:36 Steve Simon <firstname.lastname@example.org>:
> > i agree with all you say about cfs, however…
> > beware, in my experience cfs is a real win where your bandwidth to the server is low.
> > it is less helpful where the latency to the server is high (as cfs checks the file version number on every access).
> I agree with everything you said. Back on spawngrid I built some web chat application (as an additional frontend for gridchat). It used long polling for chat messages and was fully rc based (rc-httpd). You can imagine how it really was impacting server performance, basically starting processes multiple times per second. Also process IDs rocketed into the sky very fast, I've never seen numbers that high. It felt like a forkbomb.
> Then, mycroftiv told me about that and that fileserver load is very high and I had to find another solution. In my startup script I indeed just copied the executables (rc, cat, bc, ...) into a local ramfs and bound that over /bin so I don't have to change my programs. This improved everything.
> Especially for script-based applications like that I can really recommend that. It's like preloading the binaries into memory before actually loading them. Works well for static stuff.
next prev parent reply other threads:[~2022-11-04 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 19:18 Nathan Zimmen-Myers
2022-11-02 20:23 ` ori
2022-11-02 23:53 ` william
2022-11-03 0:43 ` Nathan Zimmen-Myers
2022-11-03 9:28 ` Steve Simon
2022-11-03 10:33 ` sirjofri
2022-11-03 20:57 ` Steve Simon
2022-11-04 0:00 ` william
2022-11-04 6:58 ` sirjofri
2022-11-04 7:09 ` william [this message]
2022-11-04 8:29 ` sirjofri
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).