Forum is murdering itself

[Hecktix]

72 hours is a long time of ups and downs

It's been about 2 weeks of up's and down's already, we can put up with 3 more days and then hopefully we'll be all fast and happy

[Dean]

It's been about 2 weeks of up's and down's already, we can put up with 3 more days and then hopefully we'll be all fast and happy

This is true but hopefully the next 72 hours won't be worse than the previous 2 weeks!

[Agnostic Bear]

Here's to hoping for nginx/lighttpd and IP.Board.

Ok I'm joking about IP.Board.

[Robbie]

Here's to hoping for nginx/lighttpd

I second that motion.

[beth]

this forum is dying regardless of technological issues.
you need a major overhaul of everything. it just seems a sham.

[N!ck]

A properly optimised apache won't be far off the performance of nginx. Of course, it will use much more RAM than nginx. Would probably take a lot of time and effort to switch too.

I've tuned the hell out of my apache config and nginx is now only something like 5% faster (I can't use nginx as the PHP cgi wrapper is unstable for my application).

[Agnostic Bear]

A properly optimised apache won't be far off the performance of nginx. Of course, it will use much more RAM than nginx. Would probably take a lot of time and effort to switch too.

I've tuned the hell out of my apache config and nginx is now only something like 5% faster (I can't use nginx as the PHP cgi wrapper is unstable for my application).

I'll give you a quote from a blog I was just reading:

Andreas Schipplock said:
“I appreciate your work but you are comparing a Suzuki Swift with a Lexus LS and that’s simply because Apache is dynamic in any respect and that’s what lighttpd and nginx are missing though it makes sense they exist. In fact you can even trim Apache down to the state of lighttpd and nginx but then again you would loose a lot of functionality which is mandatory in most setups.”
--------------
I’d say he’s comparing a Lexus LS and a Ferrari (if we must compare to cars). The Lexus does have a lot of niceties that the Ferrari doesn’t, but it’s also not tunable to get to 190MPH either. It isn’t just a simple case of removing the seat heaters to “trim it down”. There are deep design decisions that affect the ability of the Lexus to reach those speeds.
Similarly, Apache is process-based and Nginx (and Lighttpd) are asynchronous. This means that under load, Apache is guaranteed to do one of two things (most likely both): use tons of RAM or drop requests, because of the inherent overhead in using threads (specifically stack allocation and context-switching). Nginx and Lighttpd were written specifically to address the problems facing threaded servers under heavy load. Apache’s problems under heavy load aren’t the result of featuritis, but rather a deep architectural problem that can’t be easily addressed. On the other hand, both Nginx and Lighttpd can (and certainly will) eventually adopt all the features of Apache without heavy penalty.

[N!ck]

I'll give you a quote from a blog I was just reading:

True. But when you cut all the extra crap and gear apache towards doing specifically what you want it to do it is fast. Though with the underlying design of both, no it's never going to be as quick as nginx and nginx isn't ever going to have the features of apache.

And apache can handle loads of requests if tuned for that environment. It's shared hosting environments where it's downfall is when handling loads of simultaneous connections (Litespeed webserver is a great apache replacement for shared hosting).

It can handle 20,000+ concurrent downloads on a single server . http://www.stdlib.net/~colmmacc/Apac...he-handout.pdf

[immense]

this forum is dying regardless of technological issues.

nail. on. head.

[Callum.]

Has donator decreased?

Think it'll be interesting how much donations are received this xmas.