Wed Jan 13 04:43:36 CET 2010
I don't think mochiweb and yaws are different enough for it to matter
much in terms of performance, but in this case Yaws was probably a
better fit because they support more of the high level features that
you would use in an online backup service. Yaws certainly has more
field testing for being directly on port 80, where we run all of our
mochiweb instances behind a proxy or load balancer.
On Wed, Jan 13, 2010 at 11:25 AM, Steve Vinoski <vinoski@REDACTED> wrote:
> I'd like to read Thomas's answer to your question, but I'd also like to
> understand why you're even asking it -- why do you feel mochiweb would be
> better than yaws for this application?
> On Tue, Jan 12, 2010 at 9:29 PM, Henning Diedrich <hd2010@REDACTED>wrote:
>> Hi Thomas,
>> sounds good -- for an online backup service I would have expected mochi web
>> to come into play. What made you opt for Yaws?
>>> As a testimonial of sorts, we're using an extended Yaws and Erlang to
>>> handle substantial simultaneous upload traffic for an online backup service
>>> with quite nice results so far, performancewise. I won't go into details,
>>> but I think our current setup will be limited by the available network or
>>> disk bandwidth rather than CPU, memory, or any software bottlenecks. So
>>> switching to nginx or something like that would just be painful without
>>> providing much improved performance.
>>> (And as a bonus, because the servers just chug along ops love it :-)
>>> erlang-questions mailing list. See http://www.erlang.org/faq.html
>>> erlang-questions (at) erlang.org
>> erlang-questions mailing list. See http://www.erlang.org/faq.html
>> erlang-questions (at) erlang.org
More information about the erlang-questions