From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] Two file servers sharing an auth server
Date: Thu, 03 Nov 2022 17:00:57 -0700 [thread overview]
Message-ID: <E6055E229D48F3D865219BFC3478F0A3@thinktankworkspaces.com> (raw)
In-Reply-To: <5498E822-9183-434D-A333-C1D0C9DD890C@quintile.net>
Very interesting. I would like to hear your progress, mybe through up a page. I have thought many times to expand my network but I'm a bit cheap and the webserver seems to be doing just fine. But I might be interested in isolating werc on another node.
Quoth Steve Simon <steve@quintile.net>:
> 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).
>
> -Steve
>
> > On 3 Nov 2022, at 10:35, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
> >
> >
> > 03.11.2022 10:30:27 Steve Simon <steve@quintile.net>:
> >> having the web server boot diskless is very nice, if its content is small that is enough.
> >>
> >> for a little extra performance you can copy the web content to a ramfs at boot.
> >>
> >> if the content is big you could mount a local spinning/ssd at boot onto /usr/web and serve that, but having a diskless web and cpu servers makes things very clean and easy to maintain.
> >
> > Not to mention there's also cfs which can be nice for bigger stuff. Afaik it works by caching all accessed files on a local disk (except they're changed on the server) and all writes go to the server directly.
> >
> > sirjofri
>
next prev parent reply other threads:[~2022-11-04 0:03 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 [this message]
2022-11-04 6:58 ` sirjofri
2022-11-04 7:09 ` william
2022-11-04 8:29 ` sirjofri
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=E6055E229D48F3D865219BFC3478F0A3@thinktankworkspaces.com \
--to=william@thinktankworkspaces.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).