X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:subject:reply-to:to:references:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=xBVneWLBkIwtrZCu
	Ix2ThgDzO8Bp5WeqKPweSx2JK7xB3Z9YPUlcdXdPatfzYlXRRzxLKrySOIh5nWY2
	AV5R0pmjArARD0SwN327UwJ0v+CLM24ew/fV+sMm2jTnW6fd6UpfDrnLXg3puADr
	CvbEl5J9mhKl/hJFE3k1MHI6NoA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:subject:reply-to:to:references:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=DsTnVWOICKMAfFm0TPIg8u
	VBDqo=; b=fXqkdJe3F215Nx/FBtutCqQo1nWG+kAkqBkMkJ3peM1Q60swZQHKmg
	DUTX5U61cfT/+q9NX3/BBzXvjTGOSAZioLlDCgSST93Ote0AbrhwUmWEFor3Xd/X
	4msNKGgJUXqlZDrTrRJPbzvCKA2YIC00uPUUeGV9z7fdmotZIHHxM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=eight, glass, Brian, brian
X-HELO:	smtp-out-no.shaw.ca
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Subject:	mintty slow refresh rate over RDP
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
To:	cygwin AT cygwin DOT com
References:	<ebe91bf3-6eae-f7b7-7f54-10ad11e2fc20 AT gmail DOT com> <7339de60-cc38-ff7e-224c-0fa239962a11 AT baur-itcs DOT de> <293c3f88-ffb7-3d83-bdfb-46229887050d AT gmail DOT com> <5BFC756C DOT 50007 AT tlinx DOT org> <f26c8f0d-e5ae-0e16-208c-0f2cce4e9ad8 AT towo DOT net>
Openpgp:	preference=signencrypt
Message-ID:	<db0a3d36-f779-f684-c89e-c8ea739a60de@SystematicSw.ab.ca>
Date:	Tue, 27 Nov 2018 09:37:56 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version:	1.0
In-Reply-To:	<f26c8f0d-e5ae-0e16-208c-0f2cce4e9ad8@towo.net>
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

On 2018-11-26 16:34, Thomas Wolff wrote:
> Am 26.11.2018 um 23:36 schrieb L A Walsh:
>> On 11/26/2018 12:20 PM, David Dombrowsky wrote:
>>     I find best results hosting the GUI (the window of
>> the TTY) on the local machine, and only transfering the data
>> (the txt of the ssh session).
>>     On of the features you might want to use for your situation,
>> though, is make sure "jump-scroll" is turned on if it is not.
>> Otherwise any terminal program might take a very long time to catch
>> up.  It really is an expensive operation to scroll text on a remote
>> machine.  Early HW terminals and PC screens used special hardware
>> to perform scrolling at fast speed.  Performing a smooth scroll
>> via bit-moves of memory would be VERY painful on older machines
>> or current machines using a slow-enough remote interface.

Glass ttys needed special hardware because the early uP chips running at low
speeds with small ROMs could not do much between displaying lines.
VT100 smooth scroll with No Scroll key toggle was like having more/less built in
to the terminal; VT52 had a Scroll key which supported something similar.

> Mintty does not support smooth scrolling. (I gave it a try once but there is no
> complete implementation.)

Smooth scroll is a screen update after each scan line instead of each char line
so displays about eight times slower than jump scroll.

>>     Try running xterm locally and make sure TERM is set correctly on the
>> remote machine and I think you may be happier
>> with the performance and "feel"...

Connect using ssh (-Y or with appropriate session settings in ~/.ssh/config) to
Windows/Cygwin bash from your Linux console/term/tmux/screen session like you
would to any other Unix system.

> A good suggestion anyway.
> However, if you provide instructions on how to reproduce the issue, I may find
> time to check out whether there is some improvement potential.

Sounds like the issue is sending images of fast scrolling text over early RDP
protocol sessions which can probably only be improved by not updating the screen
as much when running under a remote session using an early protocol.
Perhaps more recent RDP protocol sessions recognized and transmitted the text
updates rather than image updates, less frequent image updates, or used some
terminal display optimizations developed over the decades since glass ttys were
replaced by term emulators.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -