Yaws (web server)
This article relies too much on references to primary sources. (April 2011) (Learn how and when to remove this template message)
2.0.5 / 11 April 2018
Because Yaws uses Erlang's lightweight threading system, it performs well under high concurrency. A load test conducted in 2002 comparing Yaws and Apache found that with the hardware tested, Apache 2.0.39 with the worker MPM failed at 4,000 concurrent connections, while Yaws continued functioning with over 80,000 concurrent connections.
The load test concludes,
"The problem with Apache is not related to the Apache code per se but is due to the manner in which the underlying operating system (Linux) implements concurrency. We believe that any system implemented using operating system threads and processes would exhibit similar performance. Erlang does not make use of the underlying OS's threads and processes for managing its own process pool and thus does not suffer from these limitations".
and in the underlined part above (formatting added), expresses the opinion that the founding technologies make the difference in scalability.
- "Releases · klacke/yaws · GitHub". Retrieved 2018-06-06.
- Steve Vinoski article at the IEEE Internet Computing review, July/August 2011
- Ghodsi, Ali. "Apache vs. Yaws". Archived from the original on May 18, 2015. Retrieved January 17, 2007.
- Official website
- Interview with YAWS developer Claes Klacke Wikstrom (OGG or MP3)
- ErlyWeb – MVC-pattern web framework for Yaws
- Erlang Web – MVC-pattern web framework Yaws and Inets Erlang/OTP application
- Nitrogen – An event-driven Web 2.0 framework for Erlang that runs on Yaws, Mochiweb, and Inets
|This Web-software-related article is a stub. You can help Wikipedia by expanding it.|