From: Vince Rice <vrice@solidrocksystems.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygwin on Win10 much slower than Win7
Date: Thu, 02 Nov 2017 18:34:00 -0000 [thread overview]
Message-ID: <1C33D0B8-66BD-43EB-B967-61FE69EFDE81@solidrocksystems.com> (raw)
In-Reply-To: <BN6PR2001MB1074E2B54834CC1E8774A8E8F15C0@BN6PR2001MB1074.namprd20.prod.outlook.com>
> On Nov 2, 2017, at 12:15 PM, Nellis, Kenneth <Kenneth.Nellis@conduent.com> wrote:
> …
> I first noticed the problem with cygpath:
> On Win 7:
>
> $ time cygpath abc
> abc
>
> real 0m0.016s
> user 0m0.000s
> sys 0m0.015s
> $
>
> On Win 10:
>
> $ time cygpath abc
> abc
>
> real 0m0.105s
> user 0m0.000s
> sys 0m0.062s
I have Win7x64 and Win10x64 VM's on the same physical Mac, both configured identically WRT disk, memory, etc. Both were just updated from setup, so are running same version of cygwin. Both were on newly started mintty's, and, in the case of Win7, just-started VM. (My Win10 VM has been up for a day or so.)
I ran cygpath 100 times in a loop (for i in {1..100} …), using the loop variable as the parameter to cygpath. I ran each loop three times, then averaged the times. Thus the times below are for 100 cygpaths.
On Win7, times were .790/.145/.396.
On Win10, times were 1.340/.350/.650.
Not enough for me to worry about, but it might be for you.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2017-11-02 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 14:50 Nellis, Kenneth
2017-11-02 13:36 ` Erik Bray
2017-11-02 13:41 ` cyg Simple
2017-11-02 16:44 ` Nellis, Kenneth
2017-11-02 16:49 ` Stephen John Smoogen
2017-11-02 17:15 ` Nellis, Kenneth
2017-11-02 18:34 ` Vince Rice [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=1C33D0B8-66BD-43EB-B967-61FE69EFDE81@solidrocksystems.com \
--to=vrice@solidrocksystems.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).