From: ludo@gnu.org (Ludovic Courtès)
To: George myglc2 Clemmer <myglc2@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Why is IceCat/GuixSD slower than Firefox/Debian on headless servers?
Date: Tue, 16 Jan 2018 17:32:17 +0100 [thread overview]
Message-ID: <87zi5d229a.fsf@gnu.org> (raw)
In-Reply-To: <86shb6bf99.fsf@gmail.com> (George myglc's message of "Mon, 15 Jan 2018 23:26:42 -0500")
George myglc2 Clemmer <myglc2@gmail.com> skribis:
> Running from a desktop to a headless server, and based on side-by-side
> clicking, IceCat/GuixSD takes ~5x times as long as Mozilla/Debian to
> respond to clicks. Further, Mozilla/Debian takes ~5x times as long as
> Mozilla running on the desktop. The bottom line: IceCat/GuixSD is
> unbearably slow.
>
> Has anyone else seen this?
I use IceCat and Conkeror on GuixSD and they’re not unbearably slow.
Ludo’.
next prev parent reply other threads:[~2018-01-16 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 4:26 Why is IceCat/GuixSD slower than Firefox/Debian on headless servers? George myglc2 Clemmer
2018-01-16 16:32 ` Ludovic Courtès [this message]
2018-01-16 19:56 ` Vladimir Sedach
2018-01-17 0:23 ` myglc2
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=87zi5d229a.fsf@gnu.org \
--to=ludo@gnu.org \
--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).