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:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; q=dns; s=default; b=PN86Nrx ICn7CoC0lVfdr49xvfFsPrLyQ/nPf7QiC7H9w4bspHBDjhcKHHPiDsdKCUAQbOtT zO0dDDvD776JyoX7mUYcDpHzIEa4dcvh73UG5Qwd16nHBXCyQfI6GSMKWdJvkL5B kiKN5p01eHlLQPzdFMPzxnvjsmfnh1EV+IQ0= 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:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; s=default; bh=up+NzSPNbQwyz c/SKJDNEOF7rRY=; b=aIw2jy6OEuHN40CT8useok3xM87g1YoV8PSIcfPusPMyP 3Mt9IxL1GfLvfHjHEMmgASonnomg4xa5zp6hOkNFetgGCOewYJUIOWcCFJlEOBLn LP26J1S5chEnBJZ++YtvRrRuWQmEk9E1LGyXr9I7oAcrDnrqJXMuk3aVAODR4I= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=eight, glass, Brian, brian X-HELO: mail-lf1-f45.google.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=KuZVw+WrWPhvq/Z/tRN4mh6FReO1515Tq3lvizJwIhE=; b=Zdr1kEmAAeiJYkHTw7QQ42sYlOUz9DJaV2d9YH0Sc4ox9PJqPYCQKJ0xplW0M5+Cs5 5lC7Q2zvTcYaPmAEQGJYALD1XCUUtnHruubJtX8lh+IcX6PAfvgE99iOpqTWLfuVk3am T65ibUzczKu5l7pi1X1wBhPHzarCOPUGnNzPK7PgP3cmxw6loGzS+/XW81wWCXukBmo9 4sDabG3D+vCeRxfPAKiNe3t38aTXZ1CQNkR15RjFbFQ300uoKItspetZVof5COG33eGp HTKSnriNZOhD72OqyLF0k5kxMU2NL86B3z7ardiDMCk0PteUxBYtp/FtplWsGhnjpR2h 5AIw== MIME-Version: 1.0 References: <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>

In-Reply-To: From: R0b0t1 Date: Tue, 27 Nov 2018 19:14:03 +0100 Message-ID: Subject: Re: mintty slow refresh rate over RDP To: Brian DOT Inglis AT systematicsw DOT ab DOT ca, cygwin AT cygwin DOT com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes On Tue, Nov 27, 2018 at 5:38 PM Brian Inglis wrote: > > 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. > While this workaround may work here, all current (2018Q4) SSH implementations do not implement Window's permission model properly and may not ever do so. Microsoft has their own port of OpenSSH and is having trouble doing this. There are some programs that will not run under SSH as it exists now, or even as packaged by Bitvise. > > 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. > More recent RDP sessions should fix this. They do not send GDI calls and instead capture the screen at intervals and compress it. There should be no traffic generated by frequent screen updates. Cheers, R0b0t1 -- 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