3 ms·
Its key to point out is that you would normally use nginx as a proxy to some other app server (nginx->mongrel) while with an erlang http server, it _is_ your ap
by jhancock 18y ago
Its key to point out is that you would normally use nginx as a proxy to some other app server (nginx->mongrel) while with an erlang http server, it _is_ your app server and you may not need to add something like nginx in front.
Its good to see all three products do well, keeping in mind the benchmark scenario is highly artificial. The results show that in the case of these three products you should make your choice based on what kind of app you need to build and trust that they each perform well.
- evgen 18y agoIn fact, most people running heavy-duty mochiweb or yaws servers will still proxy them behind nginx. Mochi or yaws can stand alone for a lot of use cases, but a good load-balancing proxy and static page cache never really hurts...
- qhoxie 18y agoResource usage can be a major factor in this too, and nginx stands alone in that respect. Having yaws using 80%+ cpu under load might be more comparable to having nginx use 40% plus the overhead of an app server.