Beyond debug it, I have none. Keep in mind that Cygwin is always going to
be slower, since its an emulated environment. That said, not allot of effort
has been put into performance issues so far.
Larry
At 02:37 PM 3/9/2001, Marcus A Martin wrote:
>I tried all of the suggestions in the email archives, but they did not help.
>Are there any other suggestions?
>
>Marcus
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Larry Hall (RFK
> > Partners, Inc)
> > Sent: Friday, March 09, 2001 12:50 PM
> > To: Marcus A Martin; [EMAIL PROTECTED]
> > Subject: Re: Gmake is slow under cygwin
> >
> >
> > Check out the -x flag on mount. It's not completely appropriate
> > in general
> > but it has been noted to speed up performance by avoiding the need to open
> > files to check if they are executables. On NTFS partitions, you can turn
> > on ntsec in the CYGWIN environment variable to get the same
> > improvement more
> > appropriately. See the user guide and the email archives in the
> > last couple
> > of months that talk about both of these options, in regard to a
> > similar issue
> > as a matter of fact.
> >
> > Larry Hall [EMAIL PROTECTED]
> > RFK Partners, Inc. http://www.rfk.com
> > 118 Washington Street (508) 893-9779 - RFK Office
> > Holliston, MA 01746 (508) 893-9889 - FAX
> >
> >
> >
> > At 12:47 PM 3/9/2001, Marcus A Martin wrote:
> > >I am writting a build environment for a large progect. We use gmake to
> > >compile or code on linux, SGI and windows 2k (via cygwin). While
> > the build
> > >environment can do all the preprocessing before a build very
> > quickly on the
> > >unix boxes, it can take up to 2 minutes on a windows box. This
> > is a serious
> > >diffence.
> > >
> > >To give you an idea of what might be causing the problem, here
> > is what our
> > >make system does. When you execute make, it calls a find command
> > to find all
> > >the files called localdefs.mk. Each localdefs.mk file contains a list of
> > >source files, defines the target as a library or an application,
> > identifies
> > >any exported headers, and then calls a make template. The make template
> > >contains the rules on how everything is built. All of the
> > localdefs.mk files
> > >are processed in memory, then make begins the compilation of any
> > file that
> > >needs to be built.
> > >
> > >The initial find takes 2-5 seconds but each localdefs.mk file takes 1-2
> > >seconds to process in memory under a cygwin/windows box. With about 150
> > >libraries and applications, the time really adds up. Do you have
> > any ideas
> > >as to how I can accelerate the windows performance?
> > >
> > >Thanks for the help,
> > >
> > >Marcus
> > >
> > >--------------------------------------------------------------
> > >A program should follow the 'Law of Least Astonishment'.
> > >What is this law? It is simply that the program should
> > > always respond to the user in the way that astonishes him least.
> > >
> > >
> > >
> > >--
> > >Want to unsubscribe from this list?
> > >Check out: http://cygwin.com/ml/#unsubscribe-simple
> >
> >
> > --
> > Want to unsubscribe from this list?
> > Check out: http://cygwin.com/ml/#unsubscribe-simple
> >
> >
>
>
>--
>Want to unsubscribe from this list?
>Check out: http://cygwin.com/ml/#unsubscribe-simple
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
