public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: cygwin@cygwin.com
Subject: Re: Looking for new apache maintainer
Date: Thu, 27 May 2004 15:13:00 -0000	[thread overview]
Message-ID: <40B60115.CF02EAF3@dessent.net> (raw)
In-Reply-To: <c94tco$re5$1@sea.gmane.org>

Andrew DeFaria wrote:

> My understanding is that the Cygwin port of Apache 1.x is also
> significantly slower than the native Apache 1.x but this didn't stop
> people from wanting a Cygwin version of 1.x. Or is there something in
> 2.x (this thread MPM thing) that would make a Cygwin port of Apache 2.x
> much, much slower than the native one?

You're correct that 1.x also suffers a performance penalty compared to
the native win32 version.  However 1.x can only operate in the prefork
mode which is not suitable to Windows since process creation is
relatively expensive.  Thus both versions are pokey.  However, with the
advent of 2.x the method of allocating workers is modular (the MPM) and
so you can choose to have them as threads or as the old prefork style,
among others.  With threads the performance under Windows is much
improved.  I suspect (but have not tested) that the Cygwin overhead
would be even more apparent in that case, because 2.x has been
specifically designed to get good performance under win32 natively,
whereas 1.x was never intended for such systems.

As far as I know the popularity of Cygwin Apache is for developing and
testing web applications that will eventually reside on unix servers. 
In that department 1.x is more popular by a huge margin due to its
stability, known quirks, and ability to work well with non-thread-safe
PHP extensions (as well as general stubbornness of sysadmins who avoid
2.x.)  Thus demand for 1.x/Cygwin should naturally be much higher as
well.  If you're actually interested in running a server then the native
version is probably better.

> BTW: Thanks for volunteering for this. Does this mean that a Cygwin
> version of mod_php would be working again?

Yes, I intend to do that.

Brian

--
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/

  parent reply	other threads:[~2004-05-27 14:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 11:38 Christopher Faylor
2004-05-27  8:19 ` Brian Dessent
2004-05-27  9:20   ` Christopher Faylor
2004-05-27  9:52   ` Max Bowsher
2004-05-27 10:05     ` Brian Dessent
2004-05-27 12:19       ` Max Bowsher
2004-05-27 12:40         ` Brian Dessent
2004-05-27 14:31       ` Andrew DeFaria
2004-05-27 14:43         ` Christopher Faylor
2004-05-27 15:13         ` Brian Dessent [this message]
2004-05-27 15:39           ` Andrew DeFaria
2004-05-27 16:09             ` Brian Dessent
2004-05-27 16:26               ` Christopher Faylor
2004-05-27 16:47                 ` Igor Pechtchanski
2004-05-27 17:18                   ` Christopher Faylor
2004-05-27 18:15                   ` Brian Dessent
2004-05-28 11:26                   ` Reini Urban
2004-05-27 21:25               ` Max Bowsher

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=40B60115.CF02EAF3@dessent.net \
    --to=brian@dessent.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).