Changeset 7a0f798b for doc/theses/thierry_delisle_PhD/thesis/text/eval_macro.tex

Timestamp:

Sep 6, 2022, 4:05:00 PM (20 months ago)

Author:

Thierry Delisle <tdelisle@…>

Branches:

ADT, ast-experimental, master, pthread-emulation

Children:

a44514e

Parents:

9f99799

Message:

Merged peter's last changes and filled in most of the TODOs

File:

• doc/theses/thierry_delisle_PhD/thesis/text/eval_macro.tex (modified) (2 diffs)

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

@@ -166 +166 @@
                 \label{fig:memcd:updt:vanilla:lat}
         }
-        \caption[Throughput and Latency results at different update rates (percentage of writes).]{Throughput and Latency results at different update rates (percentage of writes).\smallskip\newline \todo{Description}}
+        \caption[Throughput and Latency results at different update rates (percentage of writes).]{Throughput and Latency results at different update rates (percentage of writes).\smallskip\newline On the left, throughput as Desired vs Actual query rate.
+        Target QPS is the query rate that the clients are attempting to maintain and Actual QPS is the rate at which the server is able to respond.
+        On the right, tail latency, \ie 99th Percentile of the response latency as a function of \emph{desired} query rate.
+        For throughput, higher is better, for tail-latency, lower is better.
+        Each series represent 15 independent runs, the dashed lines are maximums of each series while the solid lines are the median and the dotted lines are the minimums.}
+        All runs have 15,360 client connections.
         \label{fig:memcd:updt}
 \end{figure}
@@ -194 +199 @@
 However, for the following experiments, NGINX is configured to let the master process decided the appropriate number of threads.
 
-
-% Like memcached, NGINX can be made to use multiple \glspl{kthrd}.
-% It has a very similar architecture to the memcached architecture described in Section~\ref{memcd:thrd}, where multiple \glspl{kthrd} each run a mostly independent network logic.
-% While it does not necessarily use a dedicated listening thread, each connection is arbitrarily assigned to one of the \newterm{worker} threads.
-% Each worker thread handles multiple connections exclusively, effectively dividing the connections into distinct sets.
-% Again, this is effectively the \emph{event-based server} approach.
-%
-% \cit{https://www.nginx.com/blog/inside-nginx-how-we-designed-for-performance-scale/}
-
-% NGINX 1.13.7 is an high-performance, \emph{full-service}, event-driven, with multiple operating-system processes or multiple kernel-threads within a process to handle blocking I/O.
-% It can also .
-% Concurrent connections are handled using a complex event-driven architecture.
-% The NGINX server runs a master process that performs operations such as reading configuration files, binding to ports, and controlling worker processes.
-% NGINX uses a disk-based cache for performance, and assigns a dedicated process to manage the cache.
-% This process, known as the \textit{cache manager}, is spun-off by the master process.
-% Additionally, there can be many \textit{worker processes}, each handling network connections, reading and writing disk files, and communicating with upstream servers, such as reverse proxies or databases.
-
-% A worker is a single-threaded process, running independently of other workers.
-% The worker process handles new incoming connections and processes them.
-% Workers communicate using shared memory for shared cache and session data, and other shared resources.
-% Each worker assigns
-% As in a typical event-driven architecture, the worker listens for events from the clients, and responds immediately without blocking.
-% Memory use in NGINX is very conservative, because it does not spin up a new process or thread per connection, like Apache~\cite{apache} or \CFA.
-% All operations are asynchronous -- implemented using event notifications, callback functions and fine-tuned timers.
-
 \subsection{\CFA webserver}
 The \CFA webserver is a straightforward thread-per-connection webserver, where a fixed number of \ats are created upfront.