Mongrel users - Aug 2006 - [slightly offtopic] A small, fast Apache2.2 (if there is such a thing)

Hi.

I''m using Apache2.2 built from source + mod-proxy + ssl + svn.

Everything works fine but I''m sure you I could disable a ton of
modules during the build process and in httpd.conf to speed things up
and run a tighter memory footprint.

Has anyone bothered building Apache2.2 from source disabling all the
unneeded modules.

I am planning on going through the Apache docs but I thought I''d shoot
off a quick email in case someone had already gone through the hassle.

Thanks,
Zack Chandler

On 8/24/06, Zack Chandler <zackchandler at gmail.com>
wrote:
> Hi.
>
> I''m using Apache2.2 built from source + mod-proxy + ssl + svn.
>
> Everything works fine but I''m sure you I could disable a ton of
> modules during the build process and in httpd.conf to speed things up
> and run a tighter memory footprint.
>
> Has anyone bothered building Apache2.2 from source disabling all the
> unneeded modules.
>
> I am planning on going through the Apache docs but I thought I''d
shoot
> off a quick email in case someone had already gone through the hassle.
>
> Thanks,
> Zack Chandler
You''re forced to use apache? if not, try nginx as suggested by Ezra:
 http://www.brainspl.at/articles/2006/08/23/nginx-my-new-favorite-front-end-for-mongrel-cluster

Hope that helps,

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On 8/24/06, Luis Lavena <luislavena at gmail.com>
wrote:
>
> On 8/24/06, Zack Chandler <zackchandler at gmail.com> wrote:
> > Hi.
> >
> > I''m using Apache2.2 built from source + mod-proxy + ssl +
svn.
> >
> > Everything works fine but I''m sure you I could disable a ton
of
> > modules during the build process and in httpd.conf to speed things up
> > and run a tighter memory footprint.
> >
> > Has anyone bothered building Apache2.2 from source disabling all the
> > unneeded modules.
> >
> > I am planning on going through the Apache docs but I thought
I''d shoot
> > off a quick email in case someone had already gone through the hassle.
> >
> > Thanks,
> > Zack Chandler
>
> You''re forced to use apache? if not, try nginx as suggested by
Ezra:
>
>
http://www.brainspl.at/articles/2006/08/23/nginx-my-new-favorite-front-end-for-mongrel-cluster

He has a working deployment and you''re suggesting a whole new platform
because of a blog post pimping the next hotness.  Pinch me :)

jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20060824/dd9c1acc/attachment.html

On 8/24/06, Jeremy Kemper <jeremy at bitsweat.net>
wrote:
> On 8/24/06, Luis Lavena <luislavena at gmail.com> wrote:
>
> > On 8/24/06, Zack Chandler <zackchandler at gmail.com> wrote:
> > > Hi.
> > >
> > > I''m using Apache2.2 built from source + mod-proxy + ssl
+ svn.
> > >
> > > Everything works fine but I''m sure you I could disable a
ton of
> > > modules during the build process and in httpd.conf to speed
things up
> > > and run a tighter memory footprint.
> > >
> > > Has anyone bothered building Apache2.2 from source disabling all
the
> > > unneeded modules.
> > >
> > > I am planning on going through the Apache docs but I thought
I''d shoot
> > > off a quick email in case someone had already gone through the
hassle.
> > >
> > > Thanks,
> > > Zack Chandler
> >
> > You''re forced to use apache? if not, try nginx as suggested
by Ezra:
> >
>
http://www.brainspl.at/articles/2006/08/23/nginx-my-new-favorite-front-end-for-mongrel-cluster
>
>
> He has a working deployment and you''re suggesting a whole new
platform
> because of a blog post pimping the next hotness.  Pinch me :)
Jeremy, excuse my if I didn''t see the "we are running in
production
now" sentence in that mail...

His concerns aren''t drop everything or try something new: its about
memory use and resources... why not try something different?

I don''t understand the "pinch me" sentence... what that
means? (excuse
me, I''m not a native english speaker).

>
> jeremy
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
>

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On 8/24/06, Luis Lavena <luislavena at gmail.com>
wrote:
>
> On 8/24/06, Jeremy Kemper <jeremy at bitsweat.net> wrote:
> > He has a working deployment and you''re suggesting a whole new
platform
> > because of a blog post pimping the next hotness.  Pinch me :)
>
> Jeremy, excuse my if I didn''t see the "we are running in
production
> now" sentence in that mail...
>
> His concerns aren''t drop everything or try something new: its
about
> memory use and resources... why not try something different?

Because it''s trading something that works fine but could use a bit of
tweaking for something totally unknown. That sounds fun and interesting, but
the time could be better spent working on your app.


I don''t understand the "pinch me" sentence... what that
means? (excuse
> me, I''m not a native english speaker).

People say ''pinch me'' because if it hurts, you know you
aren''t dreaming ;)

jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20060824/89508a94/attachment.html

On 8/24/06, Jeremy Kemper <jeremy at bitsweat.net>
wrote:
> On 8/24/06, Luis Lavena <luislavena at gmail.com> wrote:
>
> >
>  On 8/24/06, Jeremy Kemper <jeremy at bitsweat.net> wrote:
> > He has a working deployment and you''re suggesting a whole new
platform
> > because of a blog post pimping the next hotness.  Pinch me :)
>
> Jeremy, excuse my if I didn''t see the "we are running in
production
> now" sentence in that mail...
>
> His concerns aren''t drop everything or try something new: its
about
> memory use and resources... why not try something different?
>
> Because it''s trading something that works fine but could use a bit
of
> tweaking for something totally unknown. That sounds fun and interesting,
but
> the time could be better spent working on your app.
>
Oh, its like "don''t reinvent the wheel", often seen ALL
around
software developments, concepts and ideas...

Also, the time you spent on working in these "new things" is valuable
too, making it work faster isn''t something valuable?

Just my point of view, of course.
>
> > I don''t understand the "pinch me" sentence... what
that means? (excuse
> > me, I''m not a native english speaker).
>
>
> People say ''pinch me'' because if it hurts, you know you
aren''t dreaming ;)
>
Oh I see, though I was translating it as "you deserve a kick for your
stupid comment.", glad you explained it to me ;-)

> jeremy
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
>

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Zack,
> Has anyone bothered building Apache2.2 from source disabling all the
> unneeded modules.
I spent one rainy afternoon going through every flag and explicitly
enabling or disabling each module in Apache 2.2 that I could find.  I
paired it down to the bare minimum to meet my needs.

I''ll save you this pain.  Here''s what my configure line in my
Apache
installation script looks like:

./configure \
   --with-mpm=worker \
   --with-ssl \
   --enable-alias \
   --enable-cache \
   --enable-auth-basic \
   --enable-auth-digest \
   --enable-authn-anon \
   --enable-authn-default \
   --enable-authn-file \
   --enable-authz-default \
   --enable-authz-host \
   --enable-authz-user \
   --enable-dir \
   --enable-disk-cache \
   --enable-expires \
   --enable-mime \
   --enable-mem-cache \
   --enable-negotiation \
   --enable-deflate \
   --enable-http \
   --enable-headers \
   --enable-include \
   --enable-log-config \
   --enable-proxy \
   --enable-proxy-balancer \
   --enable-proxy-http \
   --enable-rewrite \
   --enable-setenvif \
   --enable-so \
   --enable-ssl \
   --enable-threads \
   --disable-actions \
   --disable-asis \
   --disable-authn-alias \
   --disable-authn-dbd \
   --disable-authn-dbm \
   --disable-authz-dbm \
   --disable-authz-groupfile \
   --disable-authz-ldap \
   --disable-authz-owner \
   --disable-autoindex \
   --disable-bucketeer \
   --disable-case-filter \
   --disable-case-filter-in \
   --disable-cern-meta \
   --disable-cgi \
   --disable-cgid \
   --disable-charset-lite \
   --disable-dav \
   --disable-dav-ds \
   --disable-dav-lock \
   --disable-distcache \
   --disable-dbd \
   --disable-dumpio \
   --disable-echo \
   --disable-env \
   --disable-example \
   --disable-ext-filter \
   --disable-file-cache \
   --disable-filter \
   --disable-index \
   --disable-indent \
   --disable-imagemap \
   --disable-imap \
   --disable-info \
   --disable-isapi \
   --disable-ldap \
   --disable-log-forensic \
   --disable-logio \
   --disable-mime-magic \
   --disable-nw-ssl \
   --disable-optional-fn-export \
   --disable-optional-fn-import \
   --disable-optional-hook-export \
   --disable-optional-hook-import \
   --disable-proxy-ajp \
   --disable-proxy-connect \
   --disable-proxy-ftp \
   --disable-speling \
   --disable-status \
   --disable-suexec \
   --disable-unique-id \
   --disable-userdir \
   --disable-usertrack \
   --disable-version \
   --disable-vhost-alias

While this works for my case, you may need a bit of tweaking for your
system -- I actually think there might be a few things in there I don''t
need anymore too.

BTW I would highly encourage you to script out the apache installation
process while finding the right configuration.  It''ll save you alot of
time if you have to repeat anything, and you''ll have something that
can quickly and easily install apache when you move it into production.

- --

Thanks,

Dan
__________________________________________________________________

Dan Kubb
Autopilot Marketing Inc.

Email: dan.kubb at autopilotmarketing.com
Phone: 1 (604) 820-0212
Web:   http://autopilotmarketing.com/
vCard: http://autopilotmarketing.com/~dan.kubb/vcard
__________________________________________________________________



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFE7l3E4DfZD7OEWk0RAlC9AKCmKJ3K5J2nNu6MCEduQR+OP4kAMACgtAL/
2SWHiJYiskVAGtyG80dJddA=Q/pT
-----END PGP SIGNATURE-----

On Don 24.08.2006 20:40, Luis Lavena wrote:
>On 8/24/06, Zack Chandler <zackchandler at gmail.com> wrote:
>
>You''re forced to use apache? if not, try nginx as suggested by
Ezra:
>
http://www.brainspl.at/articles/2006/08/23/nginx-my-new-favorite-front-end-for-mongrel-cluster
Thanks for link ;-))

Regards

Alex

I''m not sure how what the syntax is with apache2, I think it''s
something like --enable-static-modname, to compile apache with modules
linked statically instead of as a DSO. Depends on the module, but in
some cases there is a significant performance boost.  It will use a
bit less memory also.  Downside is that you have to recompile the
whole server every time you need to update a module.  Also, you don''t
gain anything by not compiling DSO''s.  In other words, the difference
between compiling a DSO module and then commenting it out in
httpd.conf so it''s not loaded, is the same as never compiling it in
the first place.

Statically linking everything can be a real pain.  You will probably
get what you want by just commenting out the modules you don''t need in
httpd.conf.

Chris

On 8/25/06, snacktime <snacktime at gmail.com>
wrote:
> I''m not sure how what the syntax is with apache2, I think
it''s
> something like --enable-static-modname, to compile apache with modules
> linked statically instead of as a DSO. Depends on the module, but in
> some cases there is a significant performance boost.  It will use a
> bit less memory also.  Downside is that you have to recompile the
> whole server every time you need to update a module.  Also, you
don''t
> gain anything by not compiling DSO''s.  In other words, the
difference
> between compiling a DSO module and then commenting it out in
> httpd.conf so it''s not loaded, is the same as never compiling it
in
> the first place.
>
> Statically linking everything can be a real pain.  You will probably
> get what you want by just commenting out the modules you don''t
need in
> httpd.conf.
>
> Chris
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
Chris,
  I was wondering about compiling w/ options vs. simply commenting out
the LoadModule directives... if you have a reference on this (in terms
of how it effects memory usage and speed) please send the link.

Thanks,
Zack