9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] the practicality of plan 9
Date: Sun, 30 Oct 2022 18:41:24 +0100 (GMT+01:00)	[thread overview]
Message-ID: <211de1cb-ccbd-4794-a7be-f3dce7b3d959@sirjofri.de> (raw)
In-Reply-To: <CANF_3RgxJEWY-QR4P18KzyOe0Haqh5ekQtp_hB_exrPEmWNz3w@mail.gmail.com>

Hello,

in my opinion (and experience) having a Plan 9 _grid_ is only really beneficial for larger networks (where there's a reason to have a separation for load balancing or maintenance reasons) or individuals who plan to build services with some scale. For others it's mainly playing around to learn those things or just because we can.

For example, a standard™ grid really shines with a good fileserver. I mean, it's the core of all your files and also the configuration of the other nodes in the machine. In an ideal setup you can just reboot an individual service node, or even replace it, and it just reboots using the kernel and configuration from the fileserver.

Also consider multiple users: each one can have their own terminal with a full Plan 9 kernel that's directly connected with the fileserver. You get low latency when interacting with the local kernel (e.g when running applications), but somewhat higher latency accessing files (including starting programs, though you can work around that quite easily). Big benefits are, it doesn't matter which terminal you are on, you always get the same interface to your resources (files _and_ services inside the grid), but still maintaining good speed since everything is running locally.

Well, not everything, since you can obviously off-load heavy tasks to the other servers inside your grid. Use your terminal as an interface, but do heavy tasks on big clunky machines in your network.

That's just my thoughts.

sirjofri

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td6c4be6d8502dbd0-M4909fd69995720631c9cd88f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-10-30 17:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 17:04 fig
2022-10-30 17:41 ` sirjofri [this message]
2022-10-30 18:06 ` [9fans] " adventuresin9
2022-10-30 18:24 ` [9fans] " ori
2022-11-03 17:03   ` fig
2022-11-03 19:35     ` sirjofri
2022-11-08 23:07       ` fig
2022-11-09  3:20         ` Lucio De Re
2022-11-09  3:50           ` adventuresin9
2022-11-09 23:14             ` fig
2022-11-10  3:55               ` adventuresin9
2022-11-10  4:52                 ` fig
2022-11-10 12:05                   ` hiro
2022-12-18  1:30 ` Ethan Azariah
2022-12-18 16:29   ` cinap_lenrek

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=211de1cb-ccbd-4794-a7be-f3dce7b3d959@sirjofri.de \
    --to=sirjofri+ml-9fans@sirjofri.de \
    --cc=9fans@9fans.net \
    /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).