Apache vs Yaws
sics.se
Apache vs Yaws
1–10 of 13 posts
Re: Apache vs Yaws
#2Re: Apache vs Yaws
#3Also, which apache model, prefork or worker was used?
Re: Apache vs Yaws
#4Re: Apache vs Yaws
#5Apache 2.0.39? When was this test made? Also, which apache model, prefork or worker was used?
They're essentially comparing apples to oranges:
Apache's worker MPM uses system threads, whereas Erlang uses its own internal scheduler, so that at the system level, there is only one process.
Re: Apache vs Yaws
#6Apache 2.0.39? When was this test made? Also, which apache model, prefork or worker was used?
That said, the comparison is pretty yawning. It's been known for years that Apache with its non-evented architecture is not good at handling massive amounts of connections; there's really no point at comparing with Apache anymore. I'm more interested in how this stacks up against Lighttpd or Nginx.
Re: Apache vs Yaws
#7anyone have yaws versus nginx data?
Re: Apache vs Yaws
#8Re: Apache vs Yaws
#9Erlang really rocks!