public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 09:23:58 +0100	[thread overview]
Message-ID: <54072265-4a50-4f51-8d9f-e257f1d5afa7@gmail.com> (raw)
In-Reply-To: <CAAvCNcDQa76Dp2p1xuT82NTZ9+U4i3+hVSvo7uez8EKOLa0=vA@mail.gmail.com>

On 18/12/2023 08:16, Dan Shelton via Cygwin wrote:
> On Mon, 18 Dec 2023 at 08:05, Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
>>

>>
>> 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.
> 
> Sorry, but I disagree. I think that Cygwin could compete with WSL in
> terms of performance.
> I think the issue is just bad symlink emulation for filesystems which
> do not need symlink emulation.
> 

https://cygwin.com/acronyms/#PTC

> Dan

Regards
Marco


  reply	other threads:[~2023-12-18  8:24 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
2023-12-18  7:16         ` Dan Shelton
2023-12-18  8:23           ` Marco Atzeri [this message]
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=54072265-4a50-4f51-8d9f-e257f1d5afa7@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).