From: George myglc2 Clemmer <myglc2@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to make XQuartz/MacOS <--> IceCat/GuixSD fast?
Date: Thu, 18 Jan 2018 01:15:35 -0500 [thread overview]
Message-ID: <86efmnzo8o.fsf@gmail.com> (raw)
In-Reply-To: <871sipklym.fsf@gmail.com> (Chris Marusich's message of "Tue, 16 Jan 2018 23:01:37 -0800")
On 01/16/2018 at 23:01 Chris Marusich writes:
> 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)
Thanks Chris. I used -C when forced to run X over the inet or slower
links at work but it didn't occur to me to try it on 1000BaseT. I will
check these ideas out and let you know if they make a meaningful diff.
- George
prev parent reply other threads:[~2018-01-18 6:15 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
2018-01-18 6:15 ` George myglc2 Clemmer [this message]
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=86efmnzo8o.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.