From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from b-painless.mh.aa.net.uk ([81.187.30.52]) by ur; Wed Sep 13 05:39:44 EDT 2017
Received: from 10.190.187.81.in-addr.arpa ([81.187.190.10] helo=quintile.net)
	by b-painless.mh.aa.net.uk with esmtp (Exim 4.89)
	(envelope-from <steve@quintile.net>)
	id 1ds48i-0003nL-1O
	for 9front@9front.org; Wed, 13 Sep 2017 10:39:24 +0100
Message-ID: <9d28cf335af6f495816b047f799bc62a@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Wed, 13 Sep 2017 10:39:20 +0100
To: 9front@9front.org
Subject: Re: [9front] FQA Appendix J
In-Reply-To: <CAFSF3XO6pQzsbNBZoxMMGc55rv2FUah=c6bQCkZzTYD5W9oUQw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: content-addressed open-source table rails 

First I would say rdesktop is perfectly usable on the pi, but scrolling pages
on a chrome results in rather obvious page redraws.

I believe the reason rdesktop is a bit slow from my pi to my windows laptop
(both on wired to trhe same switch) is the pi's 100BaseT NIC and
the fact that the Pi's NIC is effectively USB attached.

I have no proof of this, but that is my educated guess given that plan9
generated graphics seem quick on the Pi3.

If anyone can improve the performance of rdesktop on the pi by software means
I would be most interested but I think the limitation is hardware.

-Steve