high performance server design approach

[Fleuriot Damien]

Define "high performance" , what are your expectations in terms of concurrent connections, requests/second and all ?



Allow me to shed some measure of light here, we're running 16x web servers with nginx doing *permanent* (as in, for all requests) URL rewriting and serving 500 req/s each.

These servers admittedly running debian are behind 4x freebsd boxes using a combination of PF, CARP and relayd on 8.3-STABLE.

The web servers deliver 200mb/second worth of *small* files (roughly 1kb javascripts).
They hardly ever reach 0.25 load average, on 8 cores + hyperthreading.


What I'm getting at here is, nginx *totally rapes* performance-wise, at least for our own needs.

If it is able to deliver 500 req/s (for each server) of small files, surely it can handle the load you're planning on throwing at it ?



On Nov 13, 2012, at 11:28 AM, Friedrich Locke <friedrich.locke at gmail.com> wrote:

> Thank you Mark for suggestion, but my doubt still remains.
> 
> Regards.
> 
> On Tue, Nov 13, 2012 at 8:26 AM, Mark Blackman <mark at exonetric.com> wrote:
> 
>> On 13 Nov 2012, at 10:23, Friedrich Locke <friedrich.locke at gmail.com>
>> wrote:
>> 
>>> Hi list members,
>>> 
>>> i would like to be an http server for static content only. Due to this
>> 
>> [snip]
>> 
>>> 
>>> 
>>> What you have to say
>> 
>> benchmark nginx to see if it does the job already.
>> 
>> - Mark
>> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"