From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: tryandbuy <tryandbuy@proton.me>
Subject: Re: Performance regression in cygwin 3.4.0
Date: Thu, 8 Dec 2022 18:46:56 +0900 [thread overview]
Message-ID: <20221208184656.ea6b9796eccc503c1e238f0f@nifty.ne.jp> (raw)
In-Reply-To: <Abw9_BgkZRll8zEaAWSNVO1Uw0sF_--Amd02G5fpj3r5O6QBhyqjWu2cxV1IctJtM03OGztfZx60TEIYfDi34p3_unluAxKgQDzcsYZASxY=@proton.me>
On Wed, 07 Dec 2022 19:38:19 +0000
tryandbuy wrote:
> Reading from stdin is very slow when a process runs outside of Cygwin Terminal.
>
> Steps to reproduce:
> 1. Create "test.txt" file using python code:
> long_text = "10" * 2500
> with open(r'test.txt', 'w') as f:
> for i in range(5000):
> f.write('KEY%03d: %d => %s\n' % (i % 100, i, long_text))
>
> 2. Install "cygwin" package version > "3.3.6-1"
> 3. Open windows command prompt (cmd.exe)
> 4. Enter command:
> type test.txt | c:\cygwin64\bin\wc.exe -l
>
> When running the same command (use cat instead of type) on the Cygwin Terminal, no performance issues observed.
>
> The last version of cygwin package without issues: 3.3.6-1
> Versions of cygwin package with issues: 3.4.x - 3.5.x
>
> P.S. I tested this combinations of pipings:
> cygwin_prog | win_prog # no issues
> win_prog | cygwin_prog # has issues when running in windows command prompt, no issues in Cygwin Terminal
> cygwin_prog | cygwin_prog # has issues when running in windows command prompt, no issues in Cygwin Terminal
I confirmed the problem. I also identified the code difference,
which causes the problem, between cygwin 3.3.x and 3.4.0.
Let us consider how to fix that.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2022-12-08 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 19:38 tryandbuy
2022-12-08 9:46 ` Takashi Yano [this message]
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=20221208184656.ea6b9796eccc503c1e238f0f@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=tryandbuy@proton.me \
/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).