From: Charles Wilson <cwilson@ece.gatech.edu>
To: Ralf Habacker <Ralf.Habacker@freenet.de>
Cc: cygwin@cygwin.com
Subject: Re: AW: cygwin vfork
Date: Fri, 02 Nov 2001 01:17:00 -0000 [thread overview]
Message-ID: <3BF13F87.2070600@ece.gatech.edu> (raw)
In-Reply-To: <000101c16c39$19f18980$651c440a@BRAMSCHE>
Ralf Habacker wrote:
>> > 3) The cygwin implementation of fork-and-exec doesn't jive well with
>> > the VM size of xemacs. Supposedly a real vfork is in the works for
>> > cygwin but I can't attest to its functionality.
> Can you explain this a little bit more ? I'm asking because in
> http://sources.redhat.com/ml/cygwin-xfree/2001-q4/msg00276.html I have described
> some problems with kde2 on cygwin relating performance and I'm very interested
> in getting more informations how to fix these problems. In short, loading the
> full kde2 desktop needs about 4 minutes and the reaction time for starting apps
> are > 1 minute. This seems to be unusable.
> My assumption are that these problems depends on application loading (vfork is
> used on every app), file and socket io.
> A regular kde2 app uses about 20-40 dll's, so a faster vfork would decrease the
> loading time. :-)
Well, this is the clarification that I received:
> The VM comment is referring to the large footprint of XEmacs which means
> that doing a fork requires copying an awful lot of data (and hence takes a
> long time), most OS's do copy-on-write for vfork so the overhead is never
> incurred.
And of course, cgf chimed in on this thread, but I can't find his message
in my mail archive, and (as mentioned elsewhere) the cygwin ml archive is
missing his message as well, so I can't quote it here for you.
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
WARNING: multiple messages have this Message-ID
From: Charles Wilson <cwilson@ece.gatech.edu>
To: Ralf Habacker <Ralf.Habacker@freenet.de>
Cc: cygwin@cygwin.com
Subject: Re: AW: cygwin vfork
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <3BF13F87.2070600@ece.gatech.edu> (raw)
Message-ID: <20011111082600.ROCGJoY9p9VdjiVTqaiPTB7JdfQr8OzSF86xg9SaaSE@z> (raw)
In-Reply-To: <000101c16c39$19f18980$651c440a@BRAMSCHE>
Ralf Habacker wrote:
>> > 3) The cygwin implementation of fork-and-exec doesn't jive well with
>> > the VM size of xemacs. Supposedly a real vfork is in the works for
>> > cygwin but I can't attest to its functionality.
> Can you explain this a little bit more ? I'm asking because in
> http://sources.redhat.com/ml/cygwin-xfree/2001-q4/msg00276.html I have described
> some problems with kde2 on cygwin relating performance and I'm very interested
> in getting more informations how to fix these problems. In short, loading the
> full kde2 desktop needs about 4 minutes and the reaction time for starting apps
> are > 1 minute. This seems to be unusable.
> My assumption are that these problems depends on application loading (vfork is
> used on every app), file and socket io.
> A regular kde2 app uses about 20-40 dll's, so a faster vfork would decrease the
> loading time. :-)
Well, this is the clarification that I received:
> The VM comment is referring to the large footprint of XEmacs which means
> that doing a fork requires copying an awful lot of data (and hence takes a
> long time), most OS's do copy-on-write for vfork so the overhead is never
> incurred.
And of course, cgf chimed in on this thread, but I can't find his message
in my mail archive, and (as mentioned elsewhere) the cygwin ml archive is
missing his message as well, so I can't quote it here for you.
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-11-13 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 14:47 Charles Wilson
2001-11-01 16:27 ` Christopher Faylor
2001-11-11 8:26 ` Christopher Faylor
2001-11-01 20:08 ` Tim Prince
2001-11-11 8:26 ` Tim Prince
2001-11-01 20:56 ` AW: " Ralf Habacker
2001-11-02 1:17 ` Charles Wilson [this message]
2001-11-02 6:00 ` Christopher Faylor
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Charles Wilson
2001-11-02 6:05 ` Christopher Faylor
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` AW: " Ralf Habacker
2001-11-11 8:26 ` Ralf Habacker
2001-11-11 8:26 ` Ralf Habacker
2001-11-11 8:26 ` Charles Wilson
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=3BF13F87.2070600@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=Ralf.Habacker@freenet.de \
--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).