Apache vs. Lighttpd...

Phantum

[H]ard|Gawd
Joined
Jul 25, 2001
Messages
1,716
Title says it all; Apache vs. Lighttpd. I was wondering if anyone had thoughts or comments on this subject...?

It would appear to me that Lighttpd is actually faster and more efficient however it's prone to memory leaks. It's also far less used than Apache but it's my understanding that they both adhere to the standards pretty well.
 
I like lighttpd for basic things like static file hosting because it's quick to set up and quite simple. I don't have any experience with running active content on it. I'm looking at deploying it with a memcached backend to host gamedata for CSS/TF2 servers.

If you have a lot of apache data or .htaccess files, then that would be a pain in the ass to migrate. Lighttpd's configuration is based upon conditional statements. I was looking at their wiki page on how to get mod_rewrite functionality. I think that the conditional system provides a more uniform style for configuring various things (like the mod_rewrite equivalent).
 
Cymon, what gaming clan? I can only think of a handful of clans with those games, and a budget for that.
 
Hah, no clan.

I have a small colo set up at a high school computer club. I was never involved in any clans (as I'm quite crap at the gaming). The hardware itself is just stuff that we've pieced together over the years (the data will be hosted on a sun fire v880 with 16GB of ram, the servers on a HP dl385g3 (and potentially a whitebox dual xeon (5400)))
 
If you're not doing any serious hosting and tuning of either just run Apache there are for more resources out there for it.

If you are doing something serious and doing proper testing and config lighttpd can be much faster.
 
This will be for a personal site for my family from all over who can view it, post to it and just generally keep in touch with one another.

Later plans include a heavier emphasis on hosting, to start, for family and if all goes well then I'll scale up to allow others to host. This will start out as hosting for pictures and again, if all goes well then I'll move to a more offsite backup type scenario.
 
Later plans include a heavier emphasis on hosting, to start, for family and if all goes well then I'll scale up to allow others to host.

doing something cool for family members and friends is fine, but dont expect to jump into doing this for customers without some serious investments of both time and money. also any "hosting" or "running servers" is usually against residential ISP's terms of service. for a small website with only a dozen people using it i doubt they would even notice. but if you even think about hosting for "paying customers" with any sort of traffic volume you will need a business/commercial internet connection, among many other things.

there was a thread not too long ago about someone who wanted to get into the professional hosting game by himself and without lots of prior experience. the overwhelming concensus was "dont do it".
 
Back
Top