delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
From: | "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de> |
To: | <cygwin AT cygwin DOT com> |
Subject: | AW: cygwin vfork |
Date: | Tue, 13 Nov 2001 12:48:24 +0100 |
Message-ID: | <000101c16c39$19f18980$651c440a@BRAMSCHE> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook 8.5, Build 4.71.2173.0 |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4133.2400 |
Importance: | Normal |
In-Reply-To: | <3BF018AD.9000105@ece.gatech.edu> |
> > Seen on the XEmacs list: > > > In general the cygwin build is slower, I think this is for 3 main > > reasons: > > > > 1) gcc optimization is not as good as MSVC > > 2) The cygwin portability layer adds a lot of overhead especially > > wrt file handling. > > 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. > > Does #3 make any sense? I thought we *had* a real vfork...perhaps it > doesn't work well with large apps? > 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. :-) Regards Ralf > --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/ > > -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |