Re: web server idea

[Jason Pincin <jpincin@ashtech.net>]

This sounds excellent to me.  Although I'd love to see how khttpd works (it dounds
*really* cool), if you feel thttpd is te way to go I understand.  

I REALLY like the idea of vodka being dedicated to the DB.  It will also be
handling mail and one apache server for admin purposes, but it'll be able to devote
99.5% of that processor to the DB which is good.  Down the road, after go-live we
may be able to change it... but at this point a I want to play it safe, and that DB
is gonna be pounded.  I'm anxious to see how reverse squid helps things.  Hell...
I'm anxious to see alot of things :)

Jason


On Thu, Aug 05, 1999 at 08:09:24PM -0700, Aaron Turner wrote:
> 
> I've been trying to figure out the best way to serve static images.
> Apache with it's pre-fork model sucks- especially when you have a lot of
> people with slow connections.
> 
> Two web servers for serving statics come to mind:
> 
> thttpd: A small (2MB total RAM footprint) select() based web server that
> is secure (uses chroot) and well tested.  Also *really* fast.
> 
> khttpd: An embeded kernel module web server.  This is reported to be very
> fast as well.  Not nearly as well tested though.  Probably considered beta
> at best.
> 
> My suggestion is:
> 
> Get another IP for Yukon from NaviSite (won't be a problem), and run
> thttpd on Yukon_IP2:80. This has the advantage of:
> 
> 1) Letting Vodka worry about DB only.
> 2) Reducing CVS replication issues of images between Vodka<->Yukon.
> 3) Letting Apache worry about the PHP/mod_perl stuff and thttpd images.
> 
> Comments?
> 
> --
> Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
> Linux Knowledge Base Organization  http://linuxkb.org/
> Because world domination requires quality open documentation.