From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin a bit slow
Date: Fri, 5 Apr 2024 10:04:53 -0600 [thread overview]
Message-ID: <c971fa25-1a9e-49d0-893a-674e20de7f37@SystematicSW.ab.ca> (raw)
In-Reply-To: <CAL8MddXYCcy3w6sH31PBZ9cPvf64KUun1kHx3Vt6FHezrcG4qA@mail.gmail.com>
On 2024-04-05 09:21, J M via Cygwin wrote:
> I added, sed and grex x60 to x80, no software running and no antivirus.
> El vie., 5 abr. 2024 17:18, J M escribió:
>> I'm seeing that Cygwin is a bit slow, directly and after comparing to
>> simple ubuntu virtual machines by example.
>> Specifically:
>> - Copy and paste texts in vim, I see clearly the slow in paste.
>> - Using sed and/or grep that count approx. between 6x and 8x respect to
>> virtual machine simple ubuntu.
>> - In general multiple bash commands are slower.
>> Can you analyze this?
>> I'm use the last updated Windows 11 and a fresh Cygwin.
Any chance Cygwin may be running under Hyper-V due to possibly unrequested
security changes, such as enabling Device Security/Core Isolation/Memory
Integrity, because of enabling logging/reporting back to MS, or checking
signature on each execution of each executable, or other "security" features (by
default bypassed by buggy/unsafe MS products, which are the ones that need it)?
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2024-04-05 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 15:18 J M
2024-04-05 15:21 ` J M
2024-04-05 16:04 ` Brian Inglis [this message]
2024-04-06 8:57 ` Lee
2024-04-08 19:47 ` Adam Dinwoodie
2024-04-09 18:56 ` J M
2024-04-10 10:34 ` Christian Franke
2024-04-10 16:43 ` Sam Edge
2024-04-12 18:01 ` J M
2024-04-13 8:09 ` Sam Edge
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=c971fa25-1a9e-49d0-893a-674e20de7f37@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).