public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>
To: Stephen John Smoogen <smooge@gmail.com>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: Cygwin on Win10 much slower than Win7
Date: Thu, 02 Nov 2017 17:15:00 -0000	[thread overview]
Message-ID: <BN6PR2001MB1074E2B54834CC1E8774A8E8F15C0@BN6PR2001MB1074.namprd20.prod.outlook.com> (raw)
In-Reply-To: <CANnLRdiZPHu4KnSwNu4_qYKSU7NKZJJWUQGU2dmynLYug9y1MQ@mail.gmail.com>

From: Stephen John Smoogen
> Sent: Thursday, November 2, 2017 12:49
> To: cygwin@cygwin.com
> Subject: Re: Cygwin on Win10 much slower than Win7
> 
> On 2 November 2017 at 12:44, Nellis, Kenneth <Kenneth.Nellis@conduent.com>
> wrote:
> > From: cyg Simple
> >> On 11/2/2017 9:36 AM, Erik Bray wrote:
> >> > On Wed, Nov 1, 2017 at 3:50 PM, Nellis, Kenneth wrote:
> >> >> Since migrating from a Windows 7 laptop to one with Windows 10,
> >> >> I've noticed a significant speed decrease in opening a mintty/bash
> >> >> window from about 0.5s to 3.5s.
> >> >>
> >> >> I've narrowed it down to two bottlenecks in .bash_profile:
> >> >> to "cygpath" and "source".
> >> >>
> >> >> Each invocation of cygpath on Win10 takes about 0.12s while on
> >> >> Win7 takes only 0.016s. Both are running 64-bit Cygwin 2.9.0, and
> >> >> cygpath version 2.9.0.
> >> >>
> >> >> The files being sourced are the same, but for example, one file,
> >> >> .bash_aliases, only contains alias statements and a few variable
> >> >> assignments. On Win7, "time" says it takes 0.000s, but on Win10 it
> >> >> takes 0.023s.
> >> >>
> >> >> The Win7 CPU is "i7-4600M @ 2.90 GHz 2.90 GHz" while the
> >> >> Win10 CPU is "i7-6600U @ 2.60 GHz 2.81 GHz". I can't imagine this
> >> >> difference accounts for a 10x speed difference. Also the
> >> >> Win10 machine has an SSD compared to the Win7 machine's SCSI hard
> >> >> disk, which would favor the Win10 machine.
> >> >>
> >> >> I was wondering if anyone else noticed such a thing or could
> >> >> account for this speed difference. Can I simply blame Windows 10?
> >> >
> >> > There could be a real issue here, but for what it's worth I haven't
> >> > noticed such extreme slowdown.  But I don't have a Windows 7
> >> > machine to compare to.  I upgrade the one I'm on now from Windows 7
> >> > to Windows
> >> > 10 over a year ago, so if there ever was a difference maybe I just
> >> > got use to it and didn't notice.
> >> >
> >>
> >> Maybe a network drive connection timeout issue.  Are all of the
> >> drives that were mapped in Win7 still reachable in Win10?
> >>
> >> > I don't recall any major issues when I first upgraded either though
> >> > ¯\_(ツ)_/¯
> >> >
> >>
> >> I don't recall any either.
> >>
> >> --
> >> cyg Simple
> >
> > Yes, I dismounted all but one and same network drive on both machines,
> > and got the same results. The (faster) Win7 machine's network drive is
> > connected over WiFi while the (slower) Win10 machine over Gbit
> > Ethernet, which would seem to favor the slower machine. I hadn't
> > mentioned that the timing tests were all performed on my internal C:
> > drives, so don't think that network drives would be a factor.
> 
> One thing that might also help is how to duplicate what you are testing.
> Even without having network drives etc it could be useful for people to
> see if they are seeing speed differences or if there is something else.

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
$

--Ken Nellis

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


  reply	other threads:[~2017-11-02 17:15 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 [this message]
2017-11-02 18:34           ` Vince Rice

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=BN6PR2001MB1074E2B54834CC1E8774A8E8F15C0@BN6PR2001MB1074.namprd20.prod.outlook.com \
    --to=kenneth.nellis@conduent.com \
    --cc=cygwin@cygwin.com \
    --cc=smooge@gmail.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).