\section{Performance and stress tests}
\label{s:perftests}
-\TODO{Michal: nejak sesynchronizovat s webem}
+%\TODO{Michal: nejak sesynchronizovat s webem}
In this section we describe only the general idea of performance and stress tests of \LB components.
This work is in progress and all necessary information is updated at the wiki page:
\item All tests use sequence of events for typical jobs (small job, big job,
small DAG, big DAG) prepared beforehand. These events are stored in files in
ULM format in CVS (see \texttt{org.glite.lb.common/examples}).
-\TODO{new strategy? use real jobs...}
+%\TODO{new strategy? use real jobs...}
\item Events are generated by \verb'glite-lb-stresslog' program, which reads
ULM text of events for particular test job and logs the event sequence directly
\item Measure event throughput by
\[ \mbox{event\_throughput} = \frac{1}{\mbox{time\_delivered} - \mbox{time\_arrived}} \]
-\TODO{measure job throughput for event patterns of typical jobs or deduce
-job throughput from throughput of selected types of events?}
+%\TODO{measure job throughput for event patterns of typical jobs or deduce
+%job throughput from throughput of selected types of events?}
\item Publish the results on the web.
- \item \TODO{ETICS test framework is used to run performance and stress tests automatically.}
+% \item \TODO{ETICS test framework is used to run performance and stress tests automatically.}
\end{itemize}
% vztahuje se k cemu?
1) stresslog sends events to interlogger using the UNIX
domain socket and logd->interlogger protocol, events are
stored in files (stresslog behaves like logd)
- TODO: pro toto neni funkce v producerske knihovne
+% TODO: pro toto neni funkce v producerske knihovne
2) interlogger reads events from event files created by
stresslog (by recovery thread)
3) stresslog stores events to files and every n-th
-\subsubsection{Non-simple job states}
-\TODO{dags, collections, their states and states (and histogram) of their children/subjobs, ...}
+%\subsubsection{Non-simple job states}
+%\TODO{dags, collections, their states and states (and histogram) of their children/subjobs, ...}
-\subsection{Query tests}
-\TODO{query all my jobs, query one job, query with some structured conditions, some other queries that caused problems in the past, ...}
+%\subsection{Query tests}
+%\TODO{query all my jobs, query one job, query with some structured conditions, some other queries that caused problems in the past, ...}
\subsection{LB server and proxy combined test}
\subsection{WS interface}
-\TODO{fila, valtri: tests using Java example}
+%\TODO{fila, valtri: tests using Java example}
\req\ \path{glite-lb-bkserverd} running, events from \ref{normal} logged
\what\ retrieve both events and job states with the \LB\ WS interface
-\subsection{HTML interface}
-\TODO{fila: query tests using wget/curl}
+%\subsection{HTML interface}
+%\TODO{fila: query tests using wget/curl}
-\subsection{Change ACL}
-\TODO{kouril: to be added later with new authz schema}
+%\subsection{Change ACL}
+%\TODO{kouril: to be added later with new authz schema}
\subsection{Server purge}
-\TODO{ljocha, valtri: ozivit skript i text}
\textbf{WARNING: This test is destructive, it destroys ALL data in an
existing \LB\ database.}
\input{definitions}
\title{Logging and Bookkeeping}
-\Subtitle{Test Plan}
+\Subtitle{Test Plan Test Suite Documentation}
\author{CESNET EGEE III JRA1 and SA3 team}
\DocIdentifier{glite-lb-doc-tp-\version}
\DeliverableId{}