Comparing the performance of web server architectures

Abstract

In this paper, we extensively tune and then compare the performance of web servers based on three different server architectures. The µserver utilizes an event-driven architecture, Knot uses the highly-efficient Capriccio thread library to implement a thread-perconnection model, and WatPipe uses a hybrid of events and threads to implement a pipeline-based server that is similar in spirit to a staged event-driven architecture (SEDA) server like Haboob.We describe modifications made to the Capriccio thread library to use Linux's zero-copy sendfile interface. We then introduce the SYmmetric Multi-Processor Event Driven (SYMPED) architecture in which relatively minor modifications are made to a single process event-driven (SPED) server (the µserver) to allow it to continue processing requests in the presence of blocking due to disk accesses. Finally, we describe our C++ implementation of WatPipe, which although utilizing a pipeline-based architecture, excludes the dynamic controls over event queues and thread pools used in SEDA. When comparing the performance of these three server architectures on the workload used in our study, we arrive at different conclusions than previous studies. In spite of recent improvements to threading libraries and our further improvements to Capriccio and Knot, both the event-based µserver and pipeline-based WatPipe server provide better throughput (by about 18%). We also observe that when using blocking sockets to send data to clients, the performance obtained with some architectures is quite good and in one case is noticeably better than when using non-blocking sockets.

A high performance memory database for web application caches

“…We chose to implement both asynchronous network access and multithreading to achieve the maximum performance for the cache daemon [2]. This model is a hybrid of pure multiprocess architecture (MP) and the even-driven architecture, and is sometimes called asymmetric multi-process eventdriven (AMPED) [3].…”

Performance analysis of process driven and event driven web servers

“…This paper [7] presents a performance-oriented comparison of event-driven, thread-per-connection, and hybrid pipe lined server architectures. The Ilserver represents an event driven design, the Knot server represents a thread-per connection design, and Wat-Pipe represents a pipeline-based approach.…”

Handling input/output operations in Web servers: issues and countermeasures

“…D. Pariag et al proposes the symmetric multi‐processor event driven architecture. The symmetric multi‐processor event driven model consists of multiple SPED instances working together to increase the level of concurrency.…”

“…To resolve this issue, they introduce a hybrid model in an event dispatcher is used to identify sockets with readable contents and assign them to a server thread, which would read and process the request. D. Pariag et al [16] proposes the symmetric multi-processor event driven architecture. The symmetric multi-processor event driven model consists of multiple SPED instances working together to increase the level of concurrency.…”