From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin X11 Server slow performance
Date: Mon, 30 Apr 2018 04:45:00 -0000 [thread overview]
Message-ID: <8593bf68-d029-eddf-520b-b94565d66ff7@SystematicSw.ab.ca> (raw)
In-Reply-To: <5d579671-213c-c742-05b2-b771a827b6f5@cygwin.com>
On 2018-04-29 20:58, Yaakov Selkowitz wrote:
> On 2018-04-29 21:52, Paul Sheer wrote:
>> I am trying to use the Cygwin X11 Server on Windows 64-bit as follows:
>> C:\cygwin64\bin>XWin.exe -ac -listen tcp
>> (Note this is on a private LAN without Internet access.)
>> The X Server renders perfectly well and my favorite applications do
>> start up and run.
>> However performance is extremely slow -- it is slightly too slow to be usable.
>> For instance I tried some graphical text editors, and a [PageDown]
>> press take 0.25 seconds to render: Whereas on a commercial X Server
>> running side-by-side on the same Windows desktop renders in <0.03
>> seconds.
>> I am a bit confused if this is intended this way: i.e. is this just a
>> demonstration of the capabilities of CygWin, or is it actually being
>> used by anyone? I ask because there are no reports of anyone finding
>> the X Server slow, yet the software has been many years in release.
> Cygwin/X is most definitely being used, and this might help:
> https://x.cygwin.com/docs/ug/using-shared-memory.html
Running cygserver at system startup is definitely recommended any time you are
running many Cygwin services or processes, as when using Xwin, or cron.
I bumped all the thread counts in /etc/cygserver.conf by a factor of 4 for my
process loads.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
next prev parent reply other threads:[~2018-04-30 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABxOuY8egyTzYbXGaTeyjt0AC=Wh5KQncmu3tj35KDk4k6hENw@mail.gmail.com>
2018-04-30 2:52 ` Paul Sheer
2018-04-30 2:59 ` Yaakov Selkowitz
2018-04-30 4:45 ` Brian Inglis [this message]
2018-04-30 4:48 ` Paul Sheer
2018-04-30 10:22 ` Marco Atzeri
2018-04-30 13:20 ` Andrey Repin
2018-06-05 0:24 ` L A Walsh
2018-06-05 14:50 ` Paul Sheer
2018-06-05 16:00 ` L A Walsh
2018-06-05 16:19 ` Paul Sheer
2018-06-05 20:24 ` Marco Atzeri
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=8593bf68-d029-eddf-520b-b94565d66ff7@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@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).