public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Derek Pagel <Derek.Pagel@infor.com>
Subject: Re: Cygwin 'cp' command is still slow after Cygserver is installed
Date: Wed, 12 Apr 2023 10:10:30 -0600	[thread overview]
Message-ID: <b7726159-db7a-444f-4809-44ce00929f3f@Shaw.ca> (raw)
In-Reply-To: <CH2PR02MB602413EF22D7874353F99FF7E59B9@CH2PR02MB6024.namprd02.prod.outlook.com>

On 2023-04-12 06:44, Derek Pagel via Cygwin wrote:
>> how big are these files and from where to where are you copying them ?
>> AV interference ?
> The files being copied are not very big at all and they're just being copied
> from one directory to another on the same server.

Could be long ACL lists with many unique ACEs that need looked up on AD, and/or 
slow ADCs, and/or slow AV, and/or slow net:

for each file show the outputs of

	$ ls -dl $f
	$ getfacl $f
	$ icacls "`cygpath -m $f`"

and also attach as text, the output from strace on the cp command, as it will 
show the timing and delays e.g.

	$ strace -o cp-strace.log cp ...

-- 
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

  reply	other threads:[~2023-04-12 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 20:07 Derek Pagel
2023-04-11 21:55 ` marco atzeri
2023-04-12 12:44   ` Derek Pagel
2023-04-12 16:10     ` Brian Inglis [this message]
2023-04-14 14:10       ` Derek Pagel
2023-04-14 19:09         ` Brian Inglis
2023-04-19 13:39           ` Derek Pagel
2023-04-20  7:33             ` Andrey Repin
2023-04-26 14:37               ` Derek Pagel
2023-04-26 16:49                 ` mode -rwxrwxrwa what is execute permission a? Brian Inglis

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=b7726159-db7a-444f-4809-44ce00929f3f@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --cc=Derek.Pagel@infor.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).