Changeset 0fec6c1 for doc/theses/thierry_delisle_PhD/thesis/text/eval_macro.tex

Timestamp:

Sep 5, 2022, 9:41:11 AM (20 months ago)

Author:

Peter A. Buhr <pabuhr@…>

Branches:

ADT, ast-experimental, master, pthread-emulation

Children:

1fcbce7, 83cb754

Parents:

4dba1da

Message:

proofread conclusion chapter

File:

• doc/theses/thierry_delisle_PhD/thesis/text/eval_macro.tex (modified) (1 diff)

doc/theses/thierry_delisle_PhD/thesis/text/eval_macro.tex

@@ -182 +182 @@
 NGINX is an high-performance, \emph{full-service}, event-driven webserver.
 It can handle both static and dynamic web content, as well as serve as a reverse proxy and a load balancer~\cite{reese2008nginx}.
-This wealth of features comes with a variety of potential configuration, dictating both available features and performance.
+This wealth of capabilities comes with a variety of potential configurations, dictating available features and performance.
 The NGINX server runs a master process that performs operations such as reading configuration files, binding to ports, and controlling worker processes.
-When running as a static webserver, uses an event driven architecture to server incoming requests.
-Incoming connections are assigned a \emph{statckless} HTTP state-machine and worker processes can potentially handle thousands of these state machines.
-For the following experiment, NGINX was configured to use epoll to listen for events on these state machines and have each worker process independently accept new connections.
-Because of the realities of Linux, see Subsection~\ref{ononblock}, NGINX also maintains a pool of auxilary threads to handle block \io.
-The configuration can be used to set the number of worker processes desired, as well as the size of the auxilary pool.
-However, for the following experiments NGINX was configured to let the master process decided the appropriate number of threads.
+When running as a static webserver, it uses an event-driven architecture to service incoming requests.
+Incoming connections are assigned a \emph{stackless} HTTP state-machine and worker processes can handle thousands of these state machines.
+For the following experiment, NGINX is configured to use @epoll@ to listen for events on these state machines and have each worker process independently accept new connections.
+Because of the realities of Linux, see Subsection~\ref{ononblock}, NGINX also maintains a pool of auxiliary threads to handle blocking \io.
+The configuration can set the number of worker processes desired, as well as the size of the auxiliary pool.
+However, for the following experiments, NGINX is configured to let the master process decided the appropriate number of threads.