From: Sam Edge <sam.edgeZZZ@lineone.net>
To: cygwin@cygwin.com
Subject: Re: cygwin.bat
Date: Sun, 11 May 2003 03:31:00 -0000 [thread overview]
Message-ID: <cberbvchj7spile99755mhhikb02226t1f@4ax.com> (raw)
In-Reply-To: <20030511021835.GB18826@redhat.com>
cgf wrote in <20030511021835.GB18826@redhat.com>
in gmane.os.cygwin on Sat, 10 May 2003 22:18:35 -0400:
> >> >If you use cygwin.bat, then under Windows NT/2k/XP you first have a
> >> >CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
> >> >doing nothing until the bash.exe process exits.
> >> > [snip]
> >Negligible on a modern PC. Noticeable on some of the kit I've got
> >here. ;-)
> I *really* find that hard to believe. I've run cygwin on some pretty
> slow computers and I've never noticed a slowdown from running bash
> in a command shell. Even Windows should be smart enough to know that
> it can swap out most of command.com when bash.exe is running so I
> don't know how this could be a resource thing.
Oh yes. I've already said that the general system slow down due to one
extra waiting process isn't going to be noticeable. (Although just
because a process is swapped out doesn't mean it ceases consuming
resources, especially on Windows!)
But the overhead in /launching/ an extra CMD.EXE to process the ".BAT"
file that then starts up bash.exe can be noticed on old kit under NT.
I suspect that on Win9x the difference is much smaller because,
whether I start bash.exe directly or via cygwin.bat, a WINOA386.MOD
process is always created as well as a BASH.EXE.
--
Sam Edge
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-05-11 3:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 3:14 cygwin.bat derek
2003-05-10 3:31 ` cygwin.bat Igor Pechtchanski
2003-05-10 3:53 ` cygwin.bat derek
2003-05-10 4:01 ` cygwin.bat Larry Hall (RFK Partners, Inc.)
2003-05-10 21:56 ` cygwin.bat Sam Edge
2003-05-11 1:10 ` cygwin.bat Christopher Faylor
2003-05-11 2:18 ` cygwin.bat Sam Edge
2003-05-11 2:18 ` cygwin.bat Christopher Faylor
2003-05-11 3:31 ` Sam Edge [this message]
2003-05-11 3:50 ` cygwin.bat Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2007-11-19 16:17 cygwin.bat 123cu
2007-11-19 16:18 ` cygwin.bat Brian Mathis
2007-11-20 10:51 ` cygwin.bat Carlo Florendo
2001-09-08 15:27 cygwin.bat Bobby McNulty
2001-09-08 17:56 ` cygwin.bat Michael Erdely
2001-09-08 22:44 ` cygwin.bat Alex Malinovich
2001-09-08 15:04 cygwin.bat Alex Malinovich
2000-08-10 13:48 cygwin.bat Jonas Jensen
2000-08-10 14:01 ` cygwin.bat DJ Delorie
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=cberbvchj7spile99755mhhikb02226t1f@4ax.com \
--to=sam.edgezzz@lineone.net \
--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).