From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Derek Pagel <Derek.Pagel@infor.com>
Subject: Re: Slow cygwin programs on Windows
Date: Mon, 26 Jun 2023 20:49:12 -0600 [thread overview]
Message-ID: <fc6e4536-c387-f910-3bc1-89117a6f6356@Shaw.ca> (raw)
In-Reply-To: <CH2PR02MB6024DCB2FAC12B5F134800BAE526A@CH2PR02MB6024.namprd02.prod.outlook.com>
On 2023-06-26 11:48, Derek Pagel via Cygwin wrote:
> We are seeing more instances of application slowness due to Cygwin programs
like 'cp' and 'mv' being executed. The files being 'cp' or 'mv' are not very big
and they stay on the same server. We have installed Cygserver which has improved
things a little bit but there are still many cases of slowness afterwards. We've
been seeing most issues after moving to Windows 2019. Has anyone else
encountered a similar issue?
Do you mean Win Server 2019 or W10 1904/19H1/1909/19H2?
Helps if you show at least the output from:
$ uname -srvmo
so we can see your Cygwin and Windows releases.
Try running the same slow commands under strace e.g.
$ strace -o cp-strace.out cp ...
and attach those outputs and
$ cygcheck -hrsv > cygcheck.out
as text, and someone may be able to help you diagnose any issues.
--
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
prev parent reply other threads:[~2023-06-27 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 17:48 Derek Pagel
2023-06-27 2:49 ` Brian Inglis [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=fc6e4536-c387-f910-3bc1-89117a6f6356@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).