From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Catastrophic Cygwin find . -ls, grep performance on samba share compared to WSL&Linux
Date: Mon, 18 Dec 2023 08:05:14 +0100 [thread overview]
Message-ID: <d8c321f7-3b96-4679-aeff-bfeeb022f9b1@gmail.com> (raw)
In-Reply-To: <CAAvCNcBAiype=Ejrw_z+VMttzEawD3OuUWMW_Ys6AcHKGpVSRw@mail.gmail.com>
On 18/12/2023 07:53, Dan Shelton via Cygwin wrote:
> On Mon, 18 Dec 2023 at 07:49, Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
>>
>>
>> Is your cygserver running ?
>
> Yes, Cygserver is running
>
> Dan
Hi Dan,
the fact that you have only a factor 2 to 4 compared to WSL and Debian
tell me that Cygwin is very effective as User space enviroment.
1. time find . >/dev/null
Cygwin 86 seconds
WSL 23 seconds
Debian 19 seconds
2. time find . -ls >/dev/null
Cygwin 129 seconds
WSL 38 seconds
Debian 32 seconds
3. time grep -r -E NOMATCH 2>/dev/null
Cygwin 390 seconds
WSL 144 seconds
Debian 141 seconds
Cygwin can not go faster than the engine below and there are
several cubersome tricks to handle the POSIX compliance
I have seen worst timing trying to emulate Unix Layer on top of
a not supporting Microsoft environment.
Regards
Marco
next prev parent reply other threads:[~2023-12-18 7:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 4:08 Dan Shelton
2023-12-18 6:22 ` Dan Shelton
2023-12-18 6:49 ` Marco Atzeri
2023-12-18 6:53 ` Dan Shelton
2023-12-18 7:05 ` Marco Atzeri [this message]
2023-12-18 7:16 ` Dan Shelton
2023-12-18 8:23 ` Marco Atzeri
2023-12-20 17:20 ` Kaz Kylheku
2023-12-21 12:16 ` rfe: CYGWIN fslinktypes option? " Martin Wege
2023-12-21 16:10 ` Cedric Blancher
2023-12-21 17:43 ` Brian Inglis
2023-12-21 20:32 ` Kaz Kylheku
2023-12-24 0:47 ` Roland Mainz
2024-01-08 14:53 ` Corinna Vinschen
2023-12-22 18:53 ` Andrey Repin
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=d8c321f7-3b96-4679-aeff-bfeeb022f9b1@gmail.com \
--to=marco.atzeri@gmail.com \
--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).