public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Xfree86/cygwin and speed
Date: Fri, 09 Jan 2004 16:20:00 -0000	[thread overview]
Message-ID: <3FFED4DC.9050609@msu.edu> (raw)
In-Reply-To: <Pine.LNX.4.58.0401091705560.12132@odoaker.hrz.tu-chemnitz.de>

Alexander Gottwald wrote:
> On Fri, 9 Jan 2004 cforelle2@comcast.net wrote:
> 
> 
>>Hello all,
>>
>>I've got a question about speeding up application performance when using Xfree86 and Cygwin. Here's my configuration:
>>
>>Linux box connected by 100 Mbps Ethernet to router.
>>Windows machine connecting wirelessly at 11 Mbps (802.11b) to router.
>>
>>Cygwin with Xfree86 set up on Windows machine, X11 forwarding set up on Linux box. I connect from Windows machine to Linux box with Cygwin using ssh tunnelling. I can successfully run the Linux application remotely. All is pretty good.
>>
>>Trouble is, the application is The GIMP, and it is painfully slow on the Windows machine. Redrawing the image occurs in slow motion, and every time I move a dialog box, I've got to wait an eternity for the image to fill in. 
>>
>>Here's my question: How can I speed this up? Or, rather, where's the bottleneck?
>>
>>-Is it the 11Mbps wireless connection, in which case I'll think more deeply about shelling out for 802.11g equipment?

Yes, the problem is the wireless link.  802.11g is sufficiently fast to 
display images in Cygwin/X while 802.11b is not.  I use 802.11g at home 
all the time to get an Xdmcp session on my Linux machine and it is 
slower than 100 Mbps Ethernet, but it is fast enough to do what I need 
to do.  Dropping to 802.11b would not be acceptable for me.

Hope that helps,

Harold


  reply	other threads:[~2004-01-09 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 15:54 cforelle2
2004-01-09 16:09 ` Alexander Gottwald
2004-01-09 16:20   ` Harold L Hunt II [this message]
2004-01-09 17:31 ` Takuma Murakami

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=3FFED4DC.9050609@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@cygwin.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).