From: ori@eigenstate.org
To: steve@quintile.net
To: 9front@9front.org
Subject: Re: [9front] web browsing- vmx/vnc/rd/x2go/orher machine
Date: Wed, 09 Dec 2020 17:05:51 -0800 [thread overview]
Message-ID: <EE6015EE3659171539FE26888341A484@eigenstate.org> (raw)
In-Reply-To: <BFBB1179-1F7A-4CB8-8B29-5E22251BEB00@quintile.net>
Quoth Steve Simon <steve@quintile.net>:
>
> hi,
>
> i have not used plan9 for a couple of
> years (p9p only) but have set up a pi
> again.
>
> i have also never used 9front.
>
> what do you people use?
Personally, a mix of mothra and vnc; I've
got a smallish vultr vm that I have for vnc
when on the road, as well as my work machine
that I use as a vnc host at home.
I'm hoping to replace that with vmx, but vmx
needs some perf work.
> are there any solutions for web browsing (where
> abaco and mothra are not enough) on 9front?
There's a native netsurf port:
https://github.com/netsurf-plan9/nsport
It works ok, though it's still kind of slow
fetching over webfs.
There's some work that needs to be done still:
something to do with the scheduler making i/o
slow. Phil9 can probably fill in a bit more on
that front.
> is vxe fast enough to run linux well?
> do you use remote desktop (rd) or vnc?
> maybe you just have a 2nd machine for that?
I've found vmx frustratingly slow. But the path
to fixing it seems clear.
There are almost certainly a handful of operations
that we're doing really frequently, and we're doing
a context switch to the vmx proc on every vm exit.
A shortcut in kernel for simple, common operations
will probably speed things up quite a bit.
I need to find time to identify the operations that
matter, and write some code.
> finally, anyone any opinions on x2go which some
> claim is the most performant remote screen technology.
Heard of it -- never tried, but it's likely to be
a lot of effort to port or rewrite.
next prev parent reply other threads:[~2020-12-10 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 0:13 Steve Simon
2020-12-10 1:05 ` Kurt H Maier
2020-12-10 1:05 ` ori [this message]
2020-12-10 1:24 ` kvik
2020-12-10 1:44 ` Stanley Lieber
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=EE6015EE3659171539FE26888341A484@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=steve@quintile.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).