From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: <cygwin-talk@cygwin.com>
Subject: RE: cygwin Perl 5x slower than ActiveState?
Date: Tue, 25 Apr 2006 04:49:00 -0000 [thread overview]
Message-ID: <000b01c66823$9e113630$020aa8c0@DFW5RB41> (raw)
In-Reply-To: <043601c667c3$bcc07150$a501a8c0@CAM.ARTIMI.COM>
> From: Dave Korn
> Sent: Monday, April 24, 2006 12:23 PM
> To: cygwin@cygwin.com
> Subject: RE: cygwin Perl 5x slower than ActiveState?
>
> On 24 April 2006 18:17, Christopher Faylor wrote:
>
> > On Mon, Apr 24, 2006 at 05:51:41PM +0100, Dave Korn wrote:
> >> On 24 April 2006 16:53, Neil E. Deeds wrote:
> >>> Anyone have an idea as to why Perl runs this code so much slower
> >>> under Cygwin?
> >>
> >> Look up "emulation layer" in any good technical dictionary :)
> >
> > But, you forget. Cygwin is emulating linux and linux is
> faster than
> > Windows.
>
> That feature isn't implemented yet. PTC though!
>
> > Dave, you have to think about these things before you just fire off
> > email!
> >
> > The real solution here is to just make sure that all of the time
> > functions in Cygwin report figures which support the fact
> that Cygwin
> > is as fast as Linux.
>
> Cygwin already *is* four times faster than windows, but
> it's implemented in scaled-down step time. One second for
> cygwin is about equivalent to pi microfortnights on a real
> linux system.
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
Ah, yeah, excuse me gentlemen, I believe you're on the wrong list.
--
Gary R. Van Sickle
next parent reply other threads:[~2006-04-25 4:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <043601c667c3$bcc07150$a501a8c0@CAM.ARTIMI.COM>
2006-04-25 4:49 ` Gary R. Van Sickle [this message]
2006-04-25 10:07 ` Dave Korn
2006-04-26 3:44 ` Windows 95 Support (was mis-subjected "RE: cygwin Perl 5x slower than ActiveState?" for some unknowable reason) Gary R. Van Sickle
2006-04-28 12:32 ` Dave Korn
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='000b01c66823$9e113630$020aa8c0@DFW5RB41' \
--to=g.r.vansickle@worldnet.att.net \
--cc=cygwin-talk@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).