From: Chris Marusich <cmmarusich@gmail.com>
To: George myglc2 Clemmer <myglc2@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to make XQuartz/MacOS <--> IceCat/GuixSD fast?
Date: Tue, 16 Jan 2018 23:01:37 -0800 [thread overview]
Message-ID: <871sipklym.fsf@gmail.com> (raw)
In-Reply-To: <86tvvnasch.fsf@gmail.com> (George myglc's message of "Mon, 15 Jan 2018 13:29:18 -0500")
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
George myglc2 Clemmer <myglc2@gmail.com> writes:
> I want to speed up IceCat on my GuixSD headless server. I am using
> XQuartz/MacOS over 1000BaseT to reach a server with 3.4GHz Intel E3-1240
> V3 CPU and SSD storage. ISTM this is about as fast as one can make a
> headless server. But IceCat is unusably slow. So I wonder ...
>
> Do you run IceCat remotely from a GuixSD desktop and get good
> performance? If so, please tell me about your setup.
>
> Would Wayland make it faster?
>
> Would an upgrade to a CPU w/GPU make it faster?
>
> TIA - George
For what it's worth, I have run Firefox in similar situations (not
involving GuixSD), and I have always found it to be un-usably slow over
a remote X connection. I never bothered to try to make it faster; I'm
intrigued that you were able to make it better at all.
You may also consider doing the following to speed things up:
- Use compression (e.g., "ssh -C") (helps quite a bit in some cases)
- Limit the color palette to the fewest colors possible (helps a little)
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-17 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 18:29 How to make XQuartz/MacOS <--> IceCat/GuixSD fast? George myglc2 Clemmer
2018-01-17 0:49 ` myglc2
2018-01-17 7:01 ` Chris Marusich [this message]
2018-01-18 6:15 ` George myglc2 Clemmer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871sipklym.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).